Triple
T2177598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantius II |
E48565
|
entity |
| Predicate | dateOfElevationAsCaesar |
P37660
|
FINISHED |
| Object | 324 |
—
|
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: 324 | Statement: [Constantius II, dateOfElevationAsCaesar, 324]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfElevationAsCaesar Context triple: [Constantius II, dateOfElevationAsCaesar, 324]
-
A.
numberOfCaesaresInTetrarchy
Indicates the quantity of distinct rulers titled "Caesar" within a given instance of the Tetrarchy system.
-
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.
hasDateUnderEmperor
Indicates that an event or record occurred during the reign of a specified emperor.
-
E.
becameSeniorAugustus
Indicates that an entity assumed the role or status of senior Augustus (senior emperor) at a particular point in time.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc434978c8190b9c4dd8411b87f23 |
completed | March 7, 2026, 6:22 a.m. |
Created at: March 4, 2026, 7:45 p.m.