Triple
T18619020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meskel |
E455101
|
entity |
| Predicate | dateInGregorianCalendarLeapYear |
P70408
|
FINISHED |
| Object | September 28 |
—
|
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 28 | Statement: [Meskel, dateInGregorianCalendarLeapYear, September 28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInGregorianCalendarLeapYear Context triple: [Meskel, dateInGregorianCalendarLeapYear, September 28]
-
A.
hasDateInLeapYear
Indicates that the associated date occurs in a leap year.
-
B.
yearInGregorianCalendar
Indicates that a specified year is measured according to the Gregorian calendar system.
-
C.
hasDayCountLeapYear
Indicates that the associated day count value applies specifically to a leap year.
-
D.
newYearDateGregorianLeapOverlap
Indicates that the Gregorian calendar New Year’s date coincides or overlaps with a date defined for leap-year-related observances or calculations.
-
E.
hasDateInGregorianCalendar
chosen
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.