Triple
T3849286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Gilgit-Baltistan |
E85250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial-level government |
C638
|
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: provincial-level government Context triple: [Government of Gilgit-Baltistan, instanceOf, provincial-level government]
-
A.
provincial-level city
A provincial-level city is an urban administrative division that holds the same rank as a province or is directly governed at the provincial level, typically encompassing both a central city and surrounding rural or suburban areas.
-
B.
state government
chosen
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
C.
provincial order
A provincial order is a formal directive or regulation issued by a regional or provincial authority that governs specific activities, behaviors, or administrative procedures within its jurisdiction.
-
D.
state government office
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
-
E.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.