Triple

T10543683
Position Surface form Disambiguated ID Type / Status
Subject Battle of Birch Coulee E248758 entity
Predicate hasReinforcements P15397 FINISHED
Object relief column led from Fort Ridgely 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: relief column led from Fort Ridgely | Statement: [Battle of Birch Coulee, hasReinforcements, relief column led from Fort Ridgely]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReinforcements
Context triple: [Battle of Birch Coulee, hasReinforcements, relief column led from Fort Ridgely]
  • A. hasReserveForces
    Indicates that an entity possesses additional military or security personnel kept in reserve for potential future deployment or use.
  • B. hasApproximateDefendingForceSize
    Indicates that an entity is associated with a defending force whose size is known only approximately rather than as an exact value.
  • C. suppliedTroopsTo chosen
    Indicates that one entity provided military personnel or forces to another entity.
  • D. hasFortifications
    Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
  • E. commandingForce2Strength
    Indicates that a commanding force possesses or exerts a particular level or measure of strength.
  • 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_69d381c733c08190ab1dd6239f5f34ae completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d51911b10481909e6e548879e8de36 completed April 7, 2026, 2:47 p.m.
PD Predicate disambiguation batch_69d4fb9729288190a0149f127acd7ae3 completed April 7, 2026, 12:41 p.m.
Created at: April 6, 2026, 12:32 p.m.