Triple

T5149657
Position Surface form Disambiguated ID Type / Status
Subject The Angle E116161 entity
Predicate hasRoleInBattle P23441 FINISHED
Object focal point of Pickett's Charge 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: focal point of Pickett's Charge | Statement: [The Angle, hasRoleInBattle, focal point of Pickett's Charge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoleInBattle
Context triple: [The Angle, hasRoleInBattle, focal point of Pickett's Charge]
  • A. allyInBattle
    Indicates that two or more entities cooperate on the same side as partners during a specific battle or combat situation.
  • B. hasKeyBattle
    Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
  • C. hasCombatantSide
    Indicates a relationship where a conflict, battle, or war is associated with one of the participating sides or factions involved in the combat.
  • D. associatedWithBattle chosen
    Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
  • E. hasSubBattle
    Indicates that a larger battle or conflict includes a smaller, constituent battle as part of its overall engagement.
  • 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_69bd4446c0e08190a7c29dc74976bf03 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd78d7f4d081908d59adcd86f52f1d completed March 20, 2026, 4:42 p.m.
PD Predicate disambiguation batch_69bd77ae2f10819098bb8939106e1281 completed March 20, 2026, 4:37 p.m.
Created at: March 20, 2026, 1:43 p.m.