Triple
T8811149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saraikistan (proposed region) |
E209661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed administrative region |
C740
|
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: proposed administrative region Context triple: [Saraikistan (proposed region), instanceOf, proposed administrative region]
-
A.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
B.
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.
-
C.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
D.
province-level administrative division
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
-
E.
special administrative division
A special administrative division is a distinct territorial unit within a country that has unique legal, political, or administrative status differing from that of regular administrative regions.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.