Triple
T3932303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordian III |
E90821
|
entity |
| Predicate | becameAugustusInYear |
P37250
|
FINISHED |
| Object | 238 |
—
|
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: 238 | Statement: [Gordian III, becameAugustusInYear, 238]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameAugustusInYear Context triple: [Gordian III, becameAugustusInYear, 238]
-
A.
becameAugustusYear
chosen
Indicates the year in which a person assumed the title or status of Augustus (Roman emperor).
-
B.
dateOfElevationAsAugustus
Indicates the date on which an individual was formally elevated to the rank or title of Augustus.
-
C.
becameSeniorAugustus
Indicates that an entity assumed the role or status of senior Augustus (senior emperor) at a particular point in time.
-
D.
firstConsulshipYear
Indicates the calendar year in which an entity held its first consulship or began serving its first term as consul.
-
E.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedaaf3c881909539831bf3a8bf10 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.