Triple

T25865084
Position Surface form Disambiguated ID Type / Status
Subject Mine Run Campaign E651587 entity
Predicate casualtiesLevel P84402 FINISHED
Object relatively low compared to major battles of 1863 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: relatively low compared to major battles of 1863 | Statement: [Mine Run Campaign, casualtiesLevel, relatively low compared to major battles of 1863]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: casualtiesLevel
Context triple: [Mine Run Campaign, casualtiesLevel, relatively low compared to major battles of 1863]
  • A. hasCasualtiesLevel chosen
    Indicates the severity or extent of casualties associated with an event, incident, or situation.
  • B. casualtiesImpact
    Indicates how the number or severity of casualties affects or influences another factor, situation, or outcome.
  • C. casualties
    Indicates that an event, action, or situation resulted in people being killed or injured.
  • D. casualtiesDescription
    Indicates a textual description of the human losses (such as deaths, injuries, or missing persons) resulting from an event or incident.
  • E. casualtiesType
    Indicates the specific category or nature of casualties (e.g., killed, injured, missing) associated with an event or incident.
  • 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_69e7ab3a199c81909227cb964cacfe24 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f603bb02288190b40cedbed5b9651d completed May 2, 2026, 2:01 p.m.
PD Predicate disambiguation batch_69f602d07590819085ac34b189613104 completed May 2, 2026, 1:57 p.m.
Created at: April 22, 2026, 8:07 a.m.