Triple

T33799849
Position Surface form Disambiguated ID Type / Status
Subject John Chard E866185 entity
Predicate coCommanderAtRorkesDrift P177720 FINISHED
Object Gonville Bromhead 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: Gonville Bromhead | Statement: [John Chard, coCommanderAtRorkesDrift, Gonville Bromhead]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coCommanderAtRorkesDrift
Context triple: [John Chard, coCommanderAtRorkesDrift, Gonville Bromhead]
  • A. combatantCommander(Boer)
    Indicates that the entity serves as a military leader or commander of combatants in a conflict.
  • B. battleCommanderOnZuluSide
    Indicates that the subject served as a commanding officer for the Zulu forces in a specific battle.
  • C. escortCommander
    Indicates that one entity serves as the commanding officer responsible for leading or overseeing an escort force or mission involving another entity.
  • D. commandingConfederateForces
    Indicates that one entity holds the role or responsibility of directing and leading the military operations of the Confederate forces in relation to another entity.
  • E. commanderRole (Banastre Tarleton)
    Indicates that Banastre Tarleton held a position of command or leadership, typically over military forces or operations.
  • F. None of above. chosen

Provenance (4 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_69f3498f99f481909cb271f4965a7594 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7009d39508190af7301f824615e88 completed May 3, 2026, 8 a.m.
PD Predicate disambiguation batch_69f6fc59518081908b0275f47721d561 completed May 3, 2026, 7:42 a.m.
PDg Predicate description generation batch_69f6ffb7554881908993d6d2ffbcf8f5 completed May 3, 2026, 7:56 a.m.
Created at: May 1, 2026, 1:46 a.m.