Triple
T8227452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolt of Vercingetorix |
E192206
|
entity |
| Predicate | outcomeForVercingetorix |
P59870
|
FINISHED |
| Object | surrender at Alesia |
—
|
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: surrender at Alesia | Statement: [Revolt of Vercingetorix, outcomeForVercingetorix, surrender at Alesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForVercingetorix Context triple: [Revolt of Vercingetorix, outcomeForVercingetorix, surrender at Alesia]
-
A.
depictsVercingetorixAs
Indicates that something portrays or represents Vercingetorix in a particular way or role.
-
B.
praetorianPrefectOfGaulEnd
Indicates the time or event at which a person’s tenure as Praetorian Prefect of Gaul comes to an end.
-
C.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
E.
outcomeForOttomans
Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb77fdcb048190868ea4995b020a37 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.