Triple
T18619018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meskel |
E455101
|
entity |
| Predicate | dateInEthiopianCalendar |
P132808
|
FINISHED |
| Object | Meskerem 17 |
—
|
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: Meskerem 17 | Statement: [Meskel, dateInEthiopianCalendar, Meskerem 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInEthiopianCalendar Context triple: [Meskel, dateInEthiopianCalendar, Meskerem 17]
-
A.
dateInHebrewCalendar
Indicates that a specific date is expressed according to the Hebrew (Jewish) calendar system rather than another calendar.
-
B.
dayRelativeToEaster
Indicates the temporal offset of a given day relative to the date of Easter in a specific year (e.g., days before or after Easter Sunday).
-
C.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
D.
dateInRomanCalendar
Indicates that a given date is expressed according to the conventions and structure of the ancient Roman calendar system.
-
E.
dayInBadíCalendar
Indicates that a given day corresponds to a specific day position within the Badí (Bahá’í) 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_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_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:46 a.m.