Triple
T25119595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purépecha state urban network |
E629230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional settlement system |
C49742
|
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: regional settlement system Context triple: [Purépecha state urban network, instanceOf, regional settlement system]
-
A.
regional institutional system
A regional institutional system is a coordinated network of organizations, rules, and practices within a specific geographic area that collectively shape governance, economic activity, and social outcomes.
-
B.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
C.
Central Asian polity
A Central Asian polity is a political entity—such as a state, khanate, emirate, or tribal confederation—centered in the Central Asian region, shaped by its steppe geography, Silk Road connections, and interactions among Turkic, Persian, Mongol, and other cultural influences.
-
D.
Central Asian polity
A Central Asian polity is a historically or contemporarily organized political entity—such as a state, khanate, or empire—centered in the Central Asian region, characterized by its governance structures, territorial control, and interactions with neighboring powers.
-
E.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
- F. None of above. chosen
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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:27 a.m.