Triple
T2234646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constans |
E49250
|
entity |
| Predicate | becameAugustusYear |
P37250
|
FINISHED |
| Object | 337 |
—
|
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: 337 | Statement: [Constans, becameAugustusYear, 337]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameAugustusYear Context triple: [Constans, becameAugustusYear, 337]
-
A.
becameSeniorAugustus
Indicates that an entity assumed the role or status of senior Augustus (senior emperor) at a particular point in time.
-
B.
firstConsulshipYear
Indicates the calendar year in which an entity held its first consulship or began serving its first term as consul.
-
C.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
D.
hasNumberOfAugusti
Indicates the number of Augusti (co-emperors or senior emperors) associated with a given entity or context.
-
E.
successorAsEasternAugustus
Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09297a481909e8fe6ec645de616 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:47 p.m.