Triple
T29585252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopian New Year |
E753702
|
entity |
| Predicate | leapYearGregorianDate |
P167476
|
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: [Ethiopian New Year, leapYearGregorianDate, September 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leapYearGregorianDate Context triple: [Ethiopian New Year, leapYearGregorianDate, September 12]
-
A.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
B.
hasDateInLeapYear
Indicates that the associated date occurs in a leap year.
-
C.
leapMonthDeterminedBy
Indicates that the occurrence or placement of a leap month is determined or governed by the referenced entity or rule.
-
D.
hasDayCountLeapYear
Indicates that the associated day count value applies specifically to a leap year.
-
E.
yearInGregorianCalendar
Indicates that a specified year is measured according to the Gregorian calendar system.
- F. None of above. chosen
Provenance (4 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_69f66d7d3ac48190adef6aa96f5a5b45 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:10 p.m.