Triple
T28824688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trebonianus Gallus |
E727868
|
entity |
| Predicate | promotedToEmperorBy |
P114246
|
FINISHED |
| Object | Danubian legions |
—
|
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: Danubian legions | Statement: [Trebonianus Gallus, promotedToEmperorBy, Danubian legions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToEmperorBy Context triple: [Trebonianus Gallus, promotedToEmperorBy, Danubian legions]
-
A.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
B.
proclaimedEmperorBy
chosen
Indicates that one entity formally declares or recognizes another entity as emperor.
-
C.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
D.
proclaimedEmperorIn
Indicates that an individual was formally declared or recognized as emperor in a specific place or at a specific time.
-
E.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 6:35 a.m.