Triple
T32052443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (internal district boundary only) |
E818525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative boundary system |
C14227
|
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 boundary system Context triple: [United States (internal district boundary only), instanceOf, administrative boundary system]
-
A.
international-free subnational boundary
chosen
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.
-
B.
geographical boundary
A geographical boundary is a defined line or zone on the Earth's surface that separates distinct political, cultural, or natural regions.
-
C.
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.
-
D.
administrative division collection
A collection of administrative divisions is an organized grouping of territorial units (such as states, provinces, or districts) that together represent a structured subdivision of a larger political or geographic entity.
-
E.
international border system
An international border system is the coordinated set of legal frameworks, physical infrastructures, technologies, and administrative processes that regulate the movement of people, goods, and information between sovereign states.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:20 a.m.