Triple

T30670468
Position Surface form Disambiguated ID Type / Status
Subject Magersfontein battlefield E780778 entity
Predicate hasCommanderOnSide P203419 FINISHED
Object Boer commander Piet Cronjé 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: Boer commander Piet Cronjé | Statement: [Magersfontein battlefield, hasCommanderOnSide, Boer commander Piet Cronjé]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommanderOnSide
Context triple: [Magersfontein battlefield, hasCommanderOnSide, Boer commander Piet Cronjé]
  • A. hasCommander
    Indicates that one entity serves as the commanding officer or leader of another entity.
  • B. hasCommandersFrom
    Indicates that an entity has commanders who originate from or are associated with a specified source entity (such as a country, organization, or group).
  • C. commandersSide
    Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
  • D. commandedBySide
    Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
  • E. commandersSide1
    Indicates that the referenced commander is aligned with or belongs to the first side/party in a conflict, competition, or opposing pair.
  • 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_69f224a7fc208190a07d6d3879b31640 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a017a360f088190acd5933aa353e763 completed May 11, 2026, 6:41 a.m.
PD Predicate disambiguation batch_6a0179d3f78c8190b1d2e8829619fa54 completed May 11, 2026, 6:40 a.m.
PDg Predicate description generation batch_6a017a354d648190b036e9dad3211857 completed May 11, 2026, 6:41 a.m.
Created at: April 29, 2026, 8:31 p.m.