Triple
T29598282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geʻez era |
E754365
|
entity |
| Predicate | hasCalendarRelation |
P1818
|
FINISHED |
| Object | Ethiopian era of the Incarnation |
—
|
NE NERFINISHED |
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: Ethiopian era of the Incarnation | Statement: [Geʻez era, hasCalendarRelation, Ethiopian era of the Incarnation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalendarRelation Context triple: [Geʻez era, hasCalendarRelation, Ethiopian era of the Incarnation]
-
A.
hasCalendarStructure
Indicates that something possesses or follows a specific calendar-based organizational structure (e.g., dates, months, or scheduling framework).
-
B.
belongsToCalendar
Indicates that an event or item is associated with and contained within a specific calendar.
-
C.
hasCalendarFunction
Indicates that an entity possesses or supports a calendar-related capability or functionality.
-
D.
hasChronologyRelation
Indicates a temporal ordering relationship between entities, specifying how one relates to another in time (e.g., before, after, or overlapping).
-
E.
usesCalendar
chosen
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 6:20 p.m.