Triple
T29598277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geʻez era |
E754365
|
entity |
| Predicate | definesYearNumberingFor |
P92342
|
FINISHED |
| Object | Ethiopian ecclesiastical documents |
—
|
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: Ethiopian ecclesiastical documents | Statement: [Geʻez era, definesYearNumberingFor, Ethiopian ecclesiastical documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesYearNumberingFor Context triple: [Geʻez era, definesYearNumberingFor, Ethiopian ecclesiastical documents]
-
A.
specifiedYear
Indicates that a particular year has been explicitly designated or identified in relation to the subject.
-
B.
sharesYearNumberingWith
Indicates that two calendar systems or date representations use the same numbering for years, so a given year has the same numeric label in both.
-
C.
serializationYear
Indicates the year in which a work, content, or data was serialized or released in serialized form.
-
D.
numberingSystemBasedOn
chosen
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
E.
includesYear
Indicates that one entity contains, references, or is associated with a specific calendar year as part of its information or scope.
- 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_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 28, 2026, 6:20 p.m.