Triple

T2806275
Position Surface form Disambiguated ID Type / Status
Subject Battle of Vienna (American Civil War) E54059 entity
Predicate casualtiesConfederate P34511 FINISHED
Object light 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: light | Statement: [Battle of Vienna (American Civil War), casualtiesConfederate, light]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesConfederate
Context triple: [Battle of Vienna (American Civil War), casualtiesConfederate, light]
  • A. confederateCasualtiesAndLosses chosen
    Indicates the number or extent of casualties and material losses suffered by Confederate forces in a conflict or engagement.
  • B. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • C. casualtiesTexianKilled
    Indicates that the relationship specifies the number of Texian individuals who were killed as casualties in a particular event or conflict.
  • D. commandingConfederateForces
    Indicates that one entity holds the role or responsibility of directing and leading the military operations of the Confederate forces in relation to another entity.
  • E. coalitionCasualties
    Indicates that members of a coalition have suffered deaths or injuries as a result of a particular conflict, event, or action.
  • 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_69ab49dcee188190b5c6eca9ae9e3469 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde2ec2ac8190bd702ad3eafb6aed completed March 7, 2026, 8:13 a.m.
PD Predicate disambiguation batch_69abdd059f308190853191f6ffe2bc6f completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:59 p.m.