Triple
T34773884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anxi Protectorate |
E1002447
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frontier administrative region |
C19044
|
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: frontier administrative region Context triple: [Anxi Protectorate, instanceOf, frontier administrative region]
-
A.
frontier region
A frontier region is a sparsely settled, transitional area at the edge of established territories where political control, cultural influences, and economic systems are fluid and contested.
-
B.
frontier province
chosen
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
-
C.
frontier government
A frontier government is a provisional or early-stage governing authority established in newly settled or sparsely populated border regions to maintain order, manage resources, and extend the reach of a central state.
-
D.
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.
-
E.
autonomous prefecture
An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.