Triple

T7223158
Position Surface form Disambiguated ID Type / Status
Subject Kolb Farm E150309 entity
Predicate battleResultContext P19109 FINISHED
Object Union defensive success at Battle of Kolb’s Farm 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: Union defensive success at Battle of Kolb’s Farm | Statement: [Kolb Farm, battleResultContext, Union defensive success at Battle of Kolb’s Farm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: battleResultContext
Context triple: [Kolb Farm, battleResultContext, Union defensive success at Battle of Kolb’s Farm]
  • A. resultOfBattle chosen
    Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
  • B. battleOutcomeRole
    Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
  • C. battleOccurred
    Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
  • D. tacticalOutcome
    Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
  • E. battleOccurredNear
    Indicates that a battle took place in spatial proximity to a specified location or entity.
  • 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_69c687effb44819092b95d07d0368c9f completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e9b54a5c8190a4a289f32853a8fe completed March 27, 2026, 8:33 p.m.
PD Predicate disambiguation batch_69c6e761b7fc8190857794d78af1b468 completed March 27, 2026, 8:24 p.m.
Created at: March 27, 2026, 2:54 p.m.