Triple
T17204620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yarkand Khanate |
E417567
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Aksu |
E158489
|
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: Aksu | Statement: [Yarkand Khanate, contains, Aksu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aksu Context triple: [Yarkand Khanate, contains, Aksu]
-
A.
Aksu
chosen
Aksu is a city in northwestern China’s Xinjiang Uyghur Autonomous Region, known as an important oasis and agricultural center along the historic Silk Road.
-
B.
Aksu
Aksu is an industrial city in northeastern Kazakhstan known for its power plant and metallurgical facilities.
-
C.
Aksu
Aksu is a modern town in Antalya Province, Turkey, located near the ancient city of Perge and known for its agricultural production and growing tourism.
-
D.
Aksu River
The Aksu River is a major river in northwestern China and Kyrgyzstan that forms the principal headwater of the Tarim River in the arid Tarim Basin.
-
E.
Aksu River
The Aksu River is a significant river in southeastern Kazakhstan that flows through the Almaty Region, contributing to the area's hydrology and local ecosystems.
- 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_6a01793aec4c81908e64226986866389 |
completed | May 11, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:38 a.m.