Triple
T23405871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uvs Lake Basin Strictly Protected Area |
E559930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area in Mongolia |
C47640
|
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: protected area in Mongolia Context triple: [Uvs Lake Basin Strictly Protected Area, instanceOf, protected area in Mongolia]
-
A.
region of Mongolia
A region of Mongolia is a geographically defined area within the country characterized by distinct physical landscapes, cultural practices, and administrative or historical significance.
-
B.
province of Mongolia
A province of Mongolia is a primary administrative division of the country, governed by a local authority under national law and encompassing multiple districts, settlements, and geographic regions.
-
C.
protected area of Georgia
A protected area of Georgia is a designated geographic region within the state set aside and managed to conserve its natural, cultural, or recreational resources under specific legal and administrative safeguards.
-
D.
grassland protected area
A grassland protected area is a designated region managed to conserve natural grassland ecosystems, their biodiversity, and associated ecological processes while limiting or regulating human activities.
-
E.
Russia–Mongolia border crossing
A Russia–Mongolia border crossing is an official checkpoint where people, vehicles, and goods are inspected and processed for legal entry and exit between the Russian Federation and Mongolia.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 5:38 p.m.