Triple
T29585446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meskerem |
E753706
|
entity |
| Predicate | typicalStartGregorianLeapYear |
P84680
|
FINISHED |
| Object | September 12 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: September 12 | Statement: [Meskerem, typicalStartGregorianLeapYear, September 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartGregorianLeapYear Context triple: [Meskerem, typicalStartGregorianLeapYear, September 12]
-
A.
leapYearGregorianDate
Indicates that a given date falls in a year that is a leap year according to the rules of the Gregorian calendar.
-
B.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
C.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
D.
hasApproxGregorianStart
chosen
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
E.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
Created at: April 28, 2026, 6:10 p.m.