Triple

T15157434
Position Surface form Disambiguated ID Type / Status
Subject Battle of Insubria E362113 entity
Predicate goalOfCarthaginians P116959 FINISHED
Object incite Gallic support against Rome 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: incite Gallic support against Rome | Statement: [Battle of Insubria, goalOfCarthaginians, incite Gallic support against Rome]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: goalOfCarthaginians
Context triple: [Battle of Insubria, goalOfCarthaginians, incite Gallic support against Rome]
  • A. estimatedCarthaginianForces
    Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
  • B. CarthaginianForceType
    Indicates the type or classification of a Carthaginian military force involved in a given context or event.
  • C. CarthaginianLosses
    Indicates the number or extent of losses suffered by the Carthaginians in a given conflict or event.
  • D. aimOfRome
    Indicates that something is the goal, purpose, or intended objective of Rome.
  • E. CarthaginianCommander
    Indicates that the subject serves as a military commander for Carthage or is identified as holding a commanding role within the Carthaginian forces.
  • 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_69d85a0759908190b8a051d2e2a1cbe6 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0060c62b08190bcdbd912d011d1ba completed April 15, 2026, 9:41 p.m.
PD Predicate disambiguation batch_69deb9779acc81908ed2dad382c42dca completed April 14, 2026, 10:02 p.m.
PDg Predicate description generation batch_69dec72059c08190a34f513a00185b08 completed April 14, 2026, 11 p.m.
Created at: April 10, 2026, 3:08 a.m.