Triple
T31428606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varian Disaster |
E801731
|
entity |
| Predicate | legionsDestroyed |
P88396
|
FINISHED |
| Object | Legio XVII |
—
|
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: Legio XVII | Statement: [Varian Disaster, legionsDestroyed, Legio XVII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legionsDestroyed Context triple: [Varian Disaster, legionsDestroyed, Legio XVII]
-
A.
RomanLegionsDestroyed
chosen
Indicates that one or more Roman legions were annihilated or decisively defeated, typically resulting in their destruction as effective military units.
-
B.
casualtiesSideRomanEmpire
Indicates that the recorded casualties in a conflict or battle occurred on the side of the Roman Empire.
-
C.
CarthaginianLosses
Indicates the number or extent of losses suffered by the Carthaginians in a given conflict or event.
-
D.
RomanLegionsPresent
Indicates that Roman military legions are present at or within the specified location or context.
-
E.
ImperialLeagueForcesStrength
Indicates the level or magnitude of military power possessed by the Imperial League’s forces.
- 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_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:55 p.m.