Triple
T35045376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylitzes’ Synopsis of Histories |
E1011181
|
entity |
| Predicate | endOfNarrativeReign |
P21330
|
FINISHED |
| Object | Emperor Michael VI Bringas |
—
|
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 Michael VI Bringas | Statement: [Skylitzes’ Synopsis of Histories, endOfNarrativeReign, Emperor Michael VI Bringas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfNarrativeReign Context triple: [Skylitzes’ Synopsis of Histories, endOfNarrativeReign, Emperor Michael VI Bringas]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
endOfSecondReign
Indicates that a second period of rule or governance by an entity has concluded.
-
C.
endOfKingdom
Indicates the point or event at which a kingdom’s rule, existence, or sovereignty comes to a conclusion.
-
D.
narrativeEnd
chosen
Indicates the point or event at which a narrative, story, or discourse concludes or is brought to an end.
-
E.
endOfRebellion
Indicates that a rebellion or uprising has concluded or been brought to an end.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78596dbd881908ac257a644fac731 |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.