Triple
T14589802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andijan unrest of 2005 |
E342413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Uzbekistan |
C34984
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in Uzbekistan Context triple: [Andijan unrest of 2005, instanceOf, event in Uzbekistan]
-
A.
region of Uzbekistan
A region of Uzbekistan is a primary administrative division of the country, governed by regional authorities and comprising multiple districts, cities, and rural settlements within a defined geographic area.
-
B.
region of Turkmenistan
A region of Turkmenistan is a primary administrative division of the country, encompassing a defined geographic area with its own local governance, population, and economic activities under the national government.
-
C.
Uzbek ruling house
The Uzbek ruling house is the dynastic lineage that held political authority and sovereignty over Uzbek territories, shaping the region’s governance, culture, and historical development.
-
D.
region of Kazakhstan
A region of Kazakhstan is a primary administrative division of the country, governed by a regional authority and encompassing multiple districts, cities, and rural settlements within a defined geographic area.
-
E.
event in the War in Afghanistan (2001–2021)
An event in the War in Afghanistan (2001–2021) is a specific, temporally and geographically bounded occurrence—such as a battle, operation, attack, negotiation, or political decision—that significantly influenced the course, conduct, or consequences of the conflict.
- F. None of above. chosen
Provenance (1 batch)
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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:24 a.m.