Triple
T32231263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambiorix |
E823346
|
entity |
| Predicate | resultOfRevolt |
P9821
|
FINISHED |
| Object | Roman retaliation against the Eburones |
—
|
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: Roman retaliation against the Eburones | Statement: [Ambiorix, resultOfRevolt, Roman retaliation against the Eburones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfRevolt Context triple: [Ambiorix, resultOfRevolt, Roman retaliation against the Eburones]
-
A.
resultOfUprising
chosen
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
B.
endOfRebellion
Indicates that a rebellion or uprising has concluded or been brought to an end.
-
C.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
D.
Tambov Rebellion
Indicates an organized uprising or revolt occurring in or associated with Tambov, typically involving armed resistance against an established authority.
-
E.
revoltOccurredDuring
Indicates that a revolt took place within the temporal span of a specified event or period.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 12:39 a.m.