Triple

T26686625
Position Surface form Disambiguated ID Type / Status
Subject Boteler’s Ford E672763 entity
Predicate usedDuringBattle P4677 FINISHED
Object Battle of Antietam withdrawal 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: Battle of Antietam withdrawal | Statement: [Boteler’s Ford, usedDuringBattle, Battle of Antietam withdrawal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedDuringBattle
Context triple: [Boteler’s Ford, usedDuringBattle, Battle of Antietam withdrawal]
  • A. usedInBattle chosen
    Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
  • B. controlDuringBattle
    Indicates that one entity exerts command, influence, or strategic direction over another specifically in the context of a battle or combat situation.
  • C. conditionDuringBattle
    Indicates that a specified condition or state holds true for an entity while a particular battle or combat event is taking place.
  • D. functionDuringBattle
    Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
  • E. usedInWar
    Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
  • 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_69eecda2066c8190a344218afa5e89c1 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f61a17a7788190946f7e32d63cd43f completed May 2, 2026, 3:36 p.m.
PD Predicate disambiguation batch_69f611ab768c8190b1849c15a3e59dda completed May 2, 2026, 3 p.m.
Created at: April 27, 2026, 3:23 a.m.