Triple
T8489571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantius Chlorus |
E200932
|
entity |
| Predicate | reignAsCaesarEnd |
P83000
|
FINISHED |
| Object | 305 |
—
|
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: 305 | Statement: [Constantius Chlorus, reignAsCaesarEnd, 305]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsCaesarEnd Context triple: [Constantius Chlorus, reignAsCaesarEnd, 305]
-
A.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
B.
endEmperor
Indicates the point or event at which an individual's tenure or status as emperor comes to an end.
-
C.
reignAsKingOfTheRomansEnd
Indicates the point in time or event at which an individual's reign as King of the Romans comes to an end.
-
D.
coEmperorEnd
Indicates that one entity’s tenure as co-emperor with another entity comes to an end at a specific point in time.
-
E.
appointedCaesarYear
Indicates the year in which an individual was appointed to the position or title of Caesar.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5596f1c8190aead21a245f21c07 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:13 p.m.