Triple

T31124612
Position Surface form Disambiguated ID Type / Status
Subject Mughal conquest of Kandahar E793320 entity
Predicate opponentControlBefore P21850 FINISHED
Object Safavid control of Kandahar 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: Safavid control of Kandahar | Statement: [Mughal conquest of Kandahar, opponentControlBefore, Safavid control of Kandahar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opponentControlBefore
Context triple: [Mughal conquest of Kandahar, opponentControlBefore, Safavid control of Kandahar]
  • A. opponentAtMidway
    Indicates that one entity is the opposing side or competitor of another in the context of the Midway event, location, or stage.
  • B. opponentState
    Indicates the condition or status that an opposing party or competitor is currently in within a given context or interaction.
  • C. opponentActionEnded
    Indicates that an opposing party’s action or move has been completed or has come to an end.
  • D. controlledBefore chosen
    Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
  • E. opposedControlBy
    Indicates that one entity resists, challenges, or acts against the control or authority exerted by another 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_69f224d1701c819094f429798290e361 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6b21e7e088190832a3db585daea1c completed May 3, 2026, 2:25 a.m.
PD Predicate disambiguation batch_69f6b14faf608190a25b977c0740729c completed May 3, 2026, 2:22 a.m.
Created at: April 29, 2026, 9:05 p.m.