Triple
T27848774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guiyi Circuit |
E703894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional military-governor regime |
C27839
|
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 military-governor regime Context triple: [Guiyi Circuit, instanceOf, regional military-governor regime]
-
A.
regional settlement system
A regional settlement system is the interconnected network of cities, towns, and rural areas within a region, shaped by flows of people, goods, services, and information and structured by economic, social, and environmental relationships.
-
B.
colonial government
A colonial government is the political and administrative system imposed by a foreign power to control and manage a colony’s territory, resources, and population, typically subordinating local authority to the interests of the colonizing state.
-
C.
governor of a Roman province
A governor of a Roman province was an appointed official, often of senatorial or equestrian rank, responsible for administering justice, collecting taxes, commanding military forces, and maintaining order within a defined territorial unit of the Roman state.
-
D.
imperial governor
An imperial governor is a high-ranking official appointed by a central empire to administer, oversee, and enforce its authority, laws, and policies within a specific province or territory.
-
E.
political-military order
chosen
A political-military order is an organized entity that combines political authority with military structure and functions to pursue ideological, territorial, or governance objectives.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 6:09 p.m.