Triple
T16154515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine VIII |
E392002
|
entity |
| Predicate | coronation as co-emperor |
P46440
|
FINISHED |
| Object | 962 |
—
|
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: 962 | Statement: [Constantine VIII, coronation as co-emperor, 962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronation as co-emperor Context triple: [Constantine VIII, coronation as co-emperor, 962]
-
A.
coronationAsKingOfTheRomans
Indicates the event in which a person is formally crowned and recognized as King of the Romans.
-
B.
coronationAsCoEmperorDate
chosen
Indicates the date on which an individual was formally crowned or installed as a co-emperor alongside another reigning emperor.
-
C.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
D.
successorAsEasternAugustus
Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
-
E.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e57e95c8190ae4ed641be974ce5 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.