Triple
T17204621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarkand Khanate |
E417567
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kucha |
E520835
|
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: Kucha | Statement: [Yarkand Khanate, contains, Kucha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kucha Context triple: [Yarkand Khanate, contains, Kucha]
-
A.
Kucha
chosen
Kucha was an ancient Buddhist oasis city-state on the northern Silk Road in what is now Xinjiang, China, known for its rich cultural and artistic heritage.
-
B.
Kashgaria
Kashgaria is a historical region in what is now Xinjiang, China, centered on the oasis cities of the Tarim Basin and long contested by various Central Asian powers.
-
C.
Tokhi
Tokhi is a prominent Pashtun tribe that forms part of the larger Ghilji tribal confederation in Afghanistan.
-
D.
Kharan
Kharan is a town in Balochistan, Pakistan, serving as the administrative center of Kharan District.
-
E.
Qūchān
Qūchān is a city in northeastern Iran, located in Razavi Khorasan Province near the border with Turkmenistan.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db1e01c81909db0491fd9f49bed |
completed | April 19, 2026, 1:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fde8ba08190ae88dc9ea3366a68 |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:38 a.m.