Triple
T16463477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdulla Aripov |
E399868
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Uzbek politician |
C37488
|
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: Uzbek politician Context triple: [Abdulla Aripov, instanceOf, Uzbek politician]
-
A.
Azerbaijani politician
An Azerbaijani politician is a public figure from Azerbaijan who participates in the governance and political decision-making processes of the country, often representing a political party or constituency at local, regional, or national levels.
-
B.
Belarusian politician
A Belarusian politician is an individual actively involved in the governance, political decision-making, or public administration of Belarus, typically holding or seeking a public office within its political system.
-
C.
Uzbekistani human rights activist
An Uzbekistani human rights activist is an individual from Uzbekistan who advocates for the protection and promotion of civil, political, social, and cultural rights, often challenging government abuses and working to advance legal and social reforms.
-
D.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
E.
Hazara politician
A Hazara politician is a public officeholder or political figure of Hazara ethnic origin who participates in governance, policy-making, and representation of Hazara community interests within a political system.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.