Triple
T27752641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Pradesh–Karnataka border |
E701250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internationally recognized internal administrative boundary |
C5137
|
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: internationally recognized internal administrative boundary Context triple: [Andhra Pradesh–Karnataka border, instanceOf, internationally recognized internal administrative boundary]
-
A.
internationally recognized internal boundary
chosen
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.
-
B.
internal border
An internal border is a boundary within a single country that separates its administrative regions, jurisdictions, or territories without constituting an international frontier.
-
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.
geographical boundary
A geographical boundary is a defined line or zone on the Earth's surface that separates distinct political, cultural, or natural regions.
-
E.
international border
An international border is a legally defined geographic boundary that separates the territories and jurisdictions of two or more 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:21 p.m.