Triple
T22169927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daikundi-Uruzgan internal boundary |
E547891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal administrative boundary |
C36444
|
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: internal administrative boundary Context triple: [Daikundi-Uruzgan internal boundary, instanceOf, internal administrative boundary]
-
A.
internal border
chosen
An internal border is a boundary within a single country that separates its administrative regions, jurisdictions, or territories without constituting an international frontier.
-
B.
internationally recognized internal boundary
An internationally recognized internal boundary is an officially acknowledged dividing line within a sovereign state that separates its subnational units (such as states, provinces, or regions) and is accepted by the international community as part of that state's internal territorial organization.
-
C.
boundary review
A boundary review is a systematic evaluation and adjustment of geographic or organizational limits to ensure they remain fair, effective, and fit for current and future needs.
-
D.
political boundary
A political boundary is an officially recognized dividing line that separates the geographic areas of different political entities, such as countries, states, or municipalities, defining the limits of their jurisdiction and authority.
-
E.
international-free subnational boundary
An international-free subnational boundary is an internal administrative or political division within a country that does not coincide with or directly border any international boundary.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:34 p.m.