Property talk:P1319

Active discussions

Documentation

earliest date
earliest date at which an event could have happened. Use as qualifier for other date properties
DescriptionQualifier marking the earliest possible date of the statement where the actual date is unknown (ie. the lower bound of a specified period). Similar to start time (P580) but that isn't quite right for this usage.
Data typePoint in time
Domainhuman (Q5), event (Q1656682) (note: this should be moved to the property statements)
Allowed valuesAs standard of time/date properties. (note: this should be moved to the property statements)
Example
According to this template: Christopher Columbus (Q7322) => date of birth (P569): Unknown value => Earliest date: 31 October 1450; Isaac Asimov (Q34981) => date of birth (P569): Unknown value => Earliest date: 4 October 1919
According to statements in the property:
date of birth of Jesus (Q3016939)
When possible, data should only be stored as statements
SourceStandard authority control references. (note: this information should be moved to a property statement; use property source website for the property (P1896))
Robot and gadget jobsDeltaBot does the following jobs:
<complementary property>latest date (P1326)
See alsoage estimated by a dating method (P7584), latest start date (P8555), earliest end date (P8554)
Lists
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history
  • Chart by item creation date
  • Future dates
  • Dates in Gregorian calendar before 1582
  • Dates before year 1 (Help:Dates#Years BC)
  • Database reports/Constraint violations/P1319
  • Proposal discussionProposal discussion
    Current uses
    Total141,560
    Main statement1670.1% of uses
    Qualifier141,38499.9% of uses
    Reference9<0.1% of uses
    [create Create a translatable help page (preferably in English) for this property to be included here]
     
    Scope is as qualifier (Q54828449): the property must be used by specified way only (Help)
    Exceptions are possible as rare values may exist.
    List of this constraint violations: Database reports/Constraint violations/P1319#scope, SPARQL, SPARQL (new)
     
    This property is being used by:

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    Related property: "latest date"Edit

    latest date (P1326).--Micru (talk) 08:17, 25 June 2014 (UTC)

    Related property: "earliest date"Edit

    Moved from Property talk:P1326. --Yair rand (talk) 20:07, 29 February 2016 (UTC)

    earliest date (P1319).--Micru (talk) 08:17, 25 June 2014 (UTC)

    Good practice?Edit

    When setting this qualifier to "after 1687" as on Q11695614#P570 should date of death (P570) be set to "unknown", "1688", "17th century" or "1687 manually changed to 17th century"? --- Jura 18:34, 27 October 2015 (UTC)

    Yes, looking for guidance on this -- there are two fields now for Q514391#P570 and not sure what I should be putting there. I'm going to follow @Jura1:'s lead and put "1430s" in the death date for a composer and put "earliest date" "30 September 1436" as the qualifier. It's still not right, because he could've died in the 1440s. Mscuthbert (talk) 14:22, 16 February 2016 (UTC)
    I just simply set the value to "1436" and the precision to "century"! --Marsupium (talk) 22:25, 14 May 2016 (UTC)

    Merge with P582 ?Edit

    Moved from Property talk:P1326. --Yair rand (talk) 20:07, 29 February 2016 (UTC)

    I can't see any objective difference between properties end time (P582) and latest date (P1326). Both should be merged. Or something is missing to distinguish them if there's a difference. Verdy p (talk) 12:19, 28 February 2016 (UTC)

    Property doesn't behave as expectedEdit

    Hello, I have been wondering what is the best way to model inception (P571) dates in a museum catalogue that are expressed with date range i.e. 100BCE-200CE. As people already noted [1], it's not always clear when using earliest date (P1319) and latest date (P1326) what the placeholder for date should be (should we give the earliest date as date, and then earliest and latest dates as qualifiers? or should we change the precision level of date, with qualifiers earliest and latest date?) Unfortunately, in an expression like 100BCE-200CE, there isn't a precision level that can capture both 100BCE and 200CE. So many wiki-editors use an approximation like "Date is 1st millennium, earliest date is 100BCE, latest date is 200CE") or you might somevalue ( "Date is somevalue, earliest date is 100BCE, latest date is 200CE".

    My issue with this, however, is how earliest date (P1319) and latest date (P1326) work as constraints. I had expected that if I did a query of objects with an inception date in the BCE range, it would also include objects whose earliest date is in the BCE period. However, what I find is that with objects where someone has used somevalue or some other broad placeholder value (like 1st century, 1st millennium), these objects will not come up.

    In that case, you have to write a SPARQL query directed not at inception (P571) but at its qualifiers i.e. if I wanted to find objects whose earliest date could be in the BCE era but whose main date statement is in the CE range:

    SELECT ?archaeologicalObjectLabel ?date ?earliest ?inception WHERE {
      SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
      ?archaeologicalObject wdt:P31 wd:Q220659;
        p:P571 ?date.
      ?date pq:P1319 ?earliest;
      FILTER(?earliest < "0001"^^xsd:dateTime)
      ?archaeologicalObject wdt:P571 ?inception. 
               FILTER (?inception > "0001"^^xsd:dateTime)
    }
    LIMIT 10000

    [2]

    This is a little counterintuitive: a query for archaeological artifacts created before 1CE will not include objects that could have been created before 1CE. It means that anyone querying wikidata would need to have the savvy to search both along the inception and qualifier date property paths but I think most people would expect earliest date (P1319) and latest date (P1326) to work as limiters expressing the lower and upper range of the main date statement.

    I don't really have a clear question in mind--I just want to be sure that I am using inception (P571),earliest date (P1319) and latest date (P1326) correctly and that my understanding of how SPARQL works is correct. It also seems that lots of users are having trouble modelling date ranges and there isn't a clear community standard, so I'm curious to hear feedback from others about how to use these properties. Valeriummaximum (talk) 12:18, 17 September 2020 (UTC)

    Return to "P1319" page.