Triple

T2458549
Position Surface form Disambiguated ID Type / Status
Subject Anglo-Afghan Wars E54477 entity
Predicate involves P1256 FINISHED
Object Kandahar E72850 NE 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: Kandahar | Statement: [Anglo-Afghan Wars, involves, Kandahar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kandahar
Context triple: [Anglo-Afghan Wars, involves, Kandahar]
  • A. Kandahar chosen
    Kandahar is a historic city in southern Afghanistan that has long served as a major political, cultural, and commercial center in the region.
  • B. Kabul
    Kabul is the capital and largest city of Afghanistan, serving as its political, cultural, and economic center in the eastern part of the country.
  • C. Jalalabad, Afghanistan
    Jalalabad, Afghanistan is a major city in eastern Afghanistan near the Khyber Pass, known as a historic cultural and trade center of the region.
  • D. Kandahar Province
    Kandahar Province is a strategically important region in southern Afghanistan known for its historical role as a former capital of the Afghan empire and as a center of Pashtun culture and politics.
  • E. Khost
    Khost is a city in eastern Afghanistan known as a regional commercial and administrative center near the Pakistan border.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ab49dee84c819096b50a0049c347ac completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd10a35f88190b102a2cb5c88146e completed March 7, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69af1f82b220819084f2b5275bf3b596 completed March 9, 2026, 7:29 p.m.
Created at: March 6, 2026, 9:44 p.m.