Triple
T3570974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine IV |
E75568
|
entity |
| Predicate | yearOfCoEmperorAppointment |
P46440
|
FINISHED |
| Object | 681 |
—
|
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: 681 | Statement: [Constantine IV, yearOfCoEmperorAppointment, 681]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfCoEmperorAppointment Context triple: [Constantine IV, yearOfCoEmperorAppointment, 681]
-
A.
coronationAsCoEmperorDate
chosen
Indicates the date on which an individual was formally crowned or installed as a co-emperor alongside another reigning emperor.
-
B.
reignAsHolyRomanEmperorStart
Indicates the time point or event at which an entity begins its tenure as Holy Roman Emperor.
-
C.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
D.
successorAsEasternAugustus
Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
-
E.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0c32624819097a96b3d62e3d8f0 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.