Triple

T28692732
Position Surface form Disambiguated ID Type / Status
Subject Battle of Abrittus E729328 entity
Predicate casualtiesSideRomanEmpire P165220 FINISHED
Object very heavy 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: very heavy | Statement: [Battle of Abrittus, casualtiesSideRomanEmpire, very heavy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesSideRomanEmpire
Context triple: [Battle of Abrittus, casualtiesSideRomanEmpire, very heavy]
  • A. RomanLegionsDestroyed
    Indicates that one or more Roman legions were annihilated or decisively defeated, typically resulting in their destruction as effective military units.
  • B. eraOfRomanConquest
    Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
  • C. estimatedRomanForces
    Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
  • D. CarthaginianLosses
    Indicates the number or extent of losses suffered by the Carthaginians in a given conflict or event.
  • E. nativeCasualties
    Indicates that native or indigenous people suffered deaths or injuries as a result of a particular event, action, or conflict.
  • 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_69f043e60b6c8190ac2cd042e77fe6e9 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f65705a3048190a3728b695ba2ae65 completed May 2, 2026, 7:56 p.m.
PD Predicate disambiguation batch_69f651ac855481908e30c3b345d31356 completed May 2, 2026, 7:34 p.m.
PDg Predicate description generation batch_69f6562ef4e4819082ce6abd41b74dc5 completed May 2, 2026, 7:53 p.m.
Created at: April 28, 2026, 5:37 a.m.