Triple

T34179651
Position Surface form Disambiguated ID Type / Status
Subject Battle of Chattanooga E876776 entity
Predicate shermanRole P127151 FINISHED
Object William T. Sherman attacked Confederate right flank NE NERFINISHED

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: William T. Sherman attacked Confederate right flank | Statement: [Battle of Chattanooga, shermanRole, William T. Sherman attacked Confederate right flank]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shermanRole
Context triple: [Battle of Chattanooga, shermanRole, William T. Sherman attacked Confederate right flank]
  • A. sonRole
    Indicates that one entity holds the role or relationship of a son with respect to another entity.
  • B. supremeCommanderRole
    Indicates that one entity holds the highest-level command authority over another entity or over a defined military or organizational structure.
  • C. militaryRole
    Indicates the specific function, position, or duty an entity holds within a military organization or context.
  • D. TexianCommander
    Indicates that an entity serves as a military commander for Texian forces in a given context or event.
  • E. UnionCommanderOfAssault chosen
    Indicates that the subject served as the commanding Union officer in charge of a specific military assault.
  • 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_69f349ae640c8190b9cd220b5368d8b6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7100483748190aa8e924a5ba6dede completed May 3, 2026, 9:06 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
Created at: May 1, 2026, 1:54 a.m.