Triple
T8489572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantius Chlorus |
E200932
|
entity |
| Predicate | reignAsAugustusStart |
P37250
|
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, reignAsAugustusStart, 305]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsAugustusStart Context triple: [Constantius Chlorus, reignAsAugustusStart, 305]
-
A.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
B.
dateOfElevationAsAugustus
Indicates the date on which an individual was formally elevated to the rank or title of Augustus.
-
C.
reignAsKingOfTheRomansStart
Indicates the point in time when an individual begins their reign as King of the Romans.
-
D.
becameAugustusYear
chosen
Indicates the year in which a person assumed the title or status of Augustus (Roman emperor).
-
E.
reignAsHolyRomanEmperorStart
Indicates the time point or event at which an entity begins its tenure as Holy Roman Emperor.
- 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_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. |
Created at: March 30, 2026, 6:13 p.m.