Triple

T32160649
Position Surface form Disambiguated ID Type / Status
Subject Battle of Tel el Khuweilfe E821414 entity
Predicate commanderBelligerent2 P188444 FINISHED
Object Kress von Kressenstein 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: Kress von Kressenstein | Statement: [Battle of Tel el Khuweilfe, commanderBelligerent2, Kress von Kressenstein]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commanderBelligerent2
Context triple: [Battle of Tel el Khuweilfe, commanderBelligerent2, Kress von Kressenstein]
  • A. commanderBelligerent1
    Indicates that the subject serves as a military commander for the first belligerent party in a conflict.
  • B. opposingCommander
    Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
  • C. commanderAttacker
    Indicates that one entity serves as the commanding officer or leader of another entity that is acting as the attacker in a conflict or operation.
  • D. commander
    Indicates that one entity holds authoritative military or organizational control over another entity or group.
  • E. combatantCommander(Boer)
    Indicates that the entity serves as a military leader or commander of combatants in a conflict.
  • 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_69f34905e098819082191a6922a6d607 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
PDg Predicate description generation batch_69fba789c1188190973a919bfe2871f3 completed May 6, 2026, 8:41 p.m.
Created at: May 1, 2026, 12:32 a.m.