Triple
T10178825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier Regions |
E235928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative division of Pakistan |
C10211
|
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: former administrative division of Pakistan Context triple: [Frontier Regions, instanceOf, former administrative division of Pakistan]
-
A.
former division of Pakistan
chosen
A former division of Pakistan is an obsolete administrative unit that once functioned as an intermediate tier of government between the provincial and district levels before being abolished or reorganized.
-
B.
province of Pakistan
A province of Pakistan is a primary administrative and political subdivision of the country, governed by its own provincial government under the framework of the Pakistani constitution.
-
C.
region of Pakistan
A region of Pakistan is a geographically defined area within the country's borders characterized by shared administrative structures, cultural traits, economic activities, or environmental features.
-
D.
former state of India
A former state of India is a political and administrative unit that once existed within the Republic of India but was later dissolved, merged, renamed, or reorganized into one or more different states or union territories.
-
E.
district of British India
A district of British India was an administrative subdivision governed by colonial authorities, typically comprising multiple towns and villages, used for managing revenue collection, law and order, and local governance under the British Raj.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:11 p.m.