Triple
T29103598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boiorix |
E736702
|
entity |
| Predicate | resultAtBattleOfArausio |
P179489
|
FINISHED |
| Object | Cimbrian victory |
—
|
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: Cimbrian victory | Statement: [Boiorix, resultAtBattleOfArausio, Cimbrian victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAtBattleOfArausio Context triple: [Boiorix, resultAtBattleOfArausio, Cimbrian victory]
-
A.
militaryOutcomeAtTrebia
Indicates the result or consequence of a military engagement specifically at the Battle of Trebia.
-
B.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
C.
secondDacianWar
Indicates that an entity participates in, is associated with, or is relevant to the historical event known as the Second Dacian War.
-
D.
aftermathOfCarrhae
Indicates the state, events, or consequences that occurred as a result of the Battle of Carrhae.
-
E.
casualtiesSideRomanEmpire
Indicates that the recorded casualties in a conflict or battle occurred on the side of the Roman Empire.
- F. None of above. chosen
Provenance (4 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 11:14 a.m.