Triple
T8646763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine III |
E204995
|
entity |
| Predicate | declaredHimselfEmperorInYear |
P84111
|
FINISHED |
| Object | 407 |
—
|
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: 407 | Statement: [Constantine III, declaredHimselfEmperorInYear, 407]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredHimselfEmperorInYear Context triple: [Constantine III, declaredHimselfEmperorInYear, 407]
-
A.
coronationAsCoEmperorDate
Indicates the date on which an individual was formally crowned or installed as a co-emperor alongside another reigning emperor.
-
B.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
C.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
-
D.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
E.
definedEmperorAs
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc480eb7f88190a38d2150976cd47f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc473e44988190a3b02498e5fff668 |
completed | March 31, 2026, 10:14 p.m. |
Created at: March 30, 2026, 6:28 p.m.