Triple
T30530994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Tetrarchy |
E776998
|
entity |
| Predicate | hasAugustus |
P181157
|
FINISHED |
| Object | Galerius |
—
|
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: Galerius | Statement: [Second Tetrarchy, hasAugustus, Galerius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAugustus Context triple: [Second Tetrarchy, hasAugustus, Galerius]
-
A.
hasNumberOfAugusti
Indicates the number of Augusti (co-emperors or senior emperors) associated with a given entity or context.
-
B.
predecessorAsWesternAugustus
Indicates that one entity served as the immediately preceding holder of the title Western Augustus relative to another entity.
-
C.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
D.
reignAsAugustusEnd
Indicates the point in time at which an individual’s reign as Augustus (emperor) comes to an end.
-
E.
acclaimedAugustusBy
Indicates that one entity formally praised, honored, or recognized Augustus.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 29, 2026, 8:18 p.m.