Triple
T9595358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guba-Khachmaz economic region |
E231517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic region of Azerbaijan |
C26807
|
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: economic region of Azerbaijan Context triple: [Guba-Khachmaz economic region, instanceOf, economic region of Azerbaijan]
-
A.
district of Azerbaijan
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 Russia
An economic region of Russia is a territorial grouping of federal subjects organized for coordinated economic planning, development, and statistical analysis based on shared geographic, industrial, and infrastructural characteristics.
-
C.
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.
-
D.
region of Turkey
A region of Turkey is a large geographic and cultural area within the country, typically defined for administrative, economic, or historical purposes and encompassing multiple provinces, cities, and distinct local characteristics.
-
E.
region of Iran
A region of Iran is a geographically and culturally distinct area within the country, often defined by shared historical, ethnic, linguistic, economic, or environmental characteristics.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:07 p.m.