Triple
T29104045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flavius Gratianus |
E736714
|
entity |
| Predicate | wasMadeAugustusBy |
P82816
|
FINISHED |
| Object | Valentinian I |
—
|
NE NERFINISHED |
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: Valentinian I | Statement: [Flavius Gratianus, wasMadeAugustusBy, Valentinian I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMadeAugustusBy Context triple: [Flavius Gratianus, wasMadeAugustusBy, Valentinian I]
-
A.
wasMadeCoEmperorBy
chosen
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
B.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
C.
predecessorAsWesternAugustus
Indicates that one entity served as the immediately preceding holder of the title Western Augustus relative to another entity.
-
D.
predecessorAsEasternAugustus
Indicates that one entity previously held the position of Eastern Roman Emperor immediately before the other entity.
-
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.
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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661b842808190ac168c6f3d40d23c |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:14 a.m.