Triple

T20930323
Position Surface form Disambiguated ID Type / Status
Subject Bactra E515452 entity
Predicate hasAlternativeName P39 FINISHED
Object Baktra 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: Baktra | Statement: [Bactra, hasAlternativeName, Baktra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baktra
Context triple: [Bactra, hasAlternativeName, Baktra]
  • A. Bactria
    Bactria was an ancient historical region in Central Asia, centered around the Oxus River, known for its role as a crossroads of Persian, Greek, and later Central Asian cultures.
  • B. Tokhi
    Tokhi is a prominent Pashtun tribe that forms part of the larger Ghilji tribal confederation in Afghanistan.
  • C. Bactra chosen
    Bactra is the ancient name of Balkh, a historically significant city in northern Afghanistan that was a major center of trade, culture, and religion along the Silk Road.
  • D. Sogdia
    Sogdia was an ancient Iranian-speaking region in Central Asia, renowned as a key hub of trade and culture along the Silk Road.
  • E. Kharan
    Kharan is a town in Balochistan, Pakistan, serving as the administrative center of Kharan District.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4fb431c8190b9d40e6a72f0cc87 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f6557e4881909ce932c3f538304a completed April 21, 2026, 4 a.m.
Created at: April 16, 2026, 12:49 p.m.