Triple

T22254524
Position Surface form Disambiguated ID Type / Status
Subject John Rouse Merriott Chard E550063 entity
Predicate roleInBattleOfRorkesDrift P28183 FINISHED
Object co-commander of the British garrison 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: co-commander of the British garrison | Statement: [John Rouse Merriott Chard, roleInBattleOfRorkesDrift, co-commander of the British garrison]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfRorkesDrift
Context triple: [John Rouse Merriott Chard, roleInBattleOfRorkesDrift, co-commander of the British garrison]
  • A. roleInBattleOfBennington
    Indicates the specific role or involvement an entity had in the Battle of Bennington.
  • B. roleInWarOrConflict
    Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
  • C. foughtAs
    Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
  • D. notableBattleRole chosen
    Indicates the specific role or function an entity played in a notable or historically significant battle.
  • E. roleInAraucoWar
    Indicates the specific function, position, or involvement an entity had within the context of the Arauco 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_69e11e42adb8819087714772ea606709 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f138c1d70881908df47b0f818c0022 completed April 28, 2026, 10:46 p.m.
PD Predicate disambiguation batch_69e72fe1e0cc8190bd13cff2a0846225 completed April 21, 2026, 8:05 a.m.
Created at: April 16, 2026, 8:39 p.m.