Triple
T35045375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylitzes’ Synopsis of Histories |
E1011181
|
entity |
| Predicate | startOfNarrativeReign |
P202113
|
FINISHED |
| Object | Emperor Nikephoros I |
—
|
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: Emperor Nikephoros I | Statement: [Skylitzes’ Synopsis of Histories, startOfNarrativeReign, Emperor Nikephoros I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfNarrativeReign Context triple: [Skylitzes’ Synopsis of Histories, startOfNarrativeReign, Emperor Nikephoros I]
-
A.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
B.
marksBeginningOfDynasty
Indicates that an event, person, or moment signifies the start or formal establishment of a particular dynasty.
-
C.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
D.
worldTitleReignStart
Indicates the point in time when an entity’s reign or rule over a world or domain begins.
-
E.
reignStartAsKing
Indicates the time or event at which an individual begins their reign in the role of king.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
| PDg | Predicate description generation | batch_6a00524723408190b0294e87e5cf7715 |
completed | May 10, 2026, 9:39 a.m. |
Created at: May 3, 2026, 4:01 p.m.