Triple
T21406628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lerik District |
E528051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative district of Azerbaijan |
C20851
|
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: administrative district of Azerbaijan Context triple: [Lerik District, instanceOf, administrative district of Azerbaijan]
-
A.
district of Azerbaijan
chosen
A district of Azerbaijan is an administrative territorial unit within the country, governed by local authorities under national law and typically comprising multiple settlements, including towns and villages.
-
B.
economic region of Azerbaijan
An economic region of Azerbaijan is a territorially defined area within the country grouped by shared economic characteristics, resources, and development priorities to facilitate regional planning and management.
-
C.
district of Belarus
A district of Belarus is an administrative subdivision within a Belarusian region (oblast), responsible for local governance, public services, and implementation of national policies in its territory.
-
D.
district of Afghanistan
A district of Afghanistan is an administrative subdivision within a province, serving as a local governance unit that manages public services, security, and development for its constituent communities and settlements.
-
E.
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.
- F. None of above.
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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 5:32 p.m.