Triple
T31428609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varian Disaster |
E801731
|
entity |
| Predicate | RomanEmperorAtTime |
P97598
|
FINISHED |
| Object | Augustus |
—
|
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: Augustus | Statement: [Varian Disaster, RomanEmperorAtTime, Augustus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanEmperorAtTime Context triple: [Varian Disaster, RomanEmperorAtTime, Augustus]
-
A.
underRomanEmperor
chosen
Indicates that one entity existed, occurred, or was governed during the reign of the specified Roman emperor.
-
B.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
C.
eraOfRomanContact
Indicates the time period during which the entity was in contact or interaction with the Roman world.
-
D.
rulingEmperorPersonalName
Indicates that the specified personal name belongs to the individual who is (or was) serving as the ruling emperor.
-
E.
predecessorAsWesternAugustus
Indicates that one entity served as the immediately preceding holder of the title Western Augustus relative to 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 30, 2026, 8:55 p.m.