Triple
T2594804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodosius I |
E58202
|
entity |
| Predicate | reignStartAsSoleEmperor |
P35128
|
FINISHED |
| Object | 394 |
—
|
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: 394 | Statement: [Theodosius I, reignStartAsSoleEmperor, 394]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsSoleEmperor Context triple: [Theodosius I, reignStartAsSoleEmperor, 394]
-
A.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
-
B.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
C.
reignAsHolyRomanEmperorStart
Indicates the time point or event at which an entity begins its tenure as Holy Roman Emperor.
-
D.
startEmperor
chosen
Indicates that an entity begins its role, reign, or status as an emperor.
-
E.
succeededToThroneAs
Indicates that one entity became the new ruler by taking over the throne in a specified role or title from another entity.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd427f58c8190af1c1a9724158c96 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.