Triple

T21807167
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Bagradas River (255 BCE) E538378 entity
Predicate hasCarthaginianForceComponent P91639 FINISHED
Object war elephants 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: war elephants | Statement: [Battle of the Bagradas River (255 BCE), hasCarthaginianForceComponent, war elephants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCarthaginianForceComponent
Context triple: [Battle of the Bagradas River (255 BCE), hasCarthaginianForceComponent, war elephants]
  • A. estimatedCarthaginianForces
    Indicates an assessment or approximation of the size or strength of the military forces associated with Carthage.
  • B. CarthaginianForceType chosen
    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. goalOfCarthaginians
    Indicates that the specified objective or aim is held or pursued by the Carthaginians.
  • 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.

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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07803b4888190af06bf7a90198f60 completed April 28, 2026, 9:04 a.m.
PD Predicate disambiguation batch_69e6be751ce881909badced245ef76c7 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:53 p.m.