Triple
T37903245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Colorado |
E945475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era territory |
C5628
|
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: colonial-era territory Context triple: [Spanish Colorado, instanceOf, colonial-era territory]
-
A.
colonial territory
chosen
A colonial territory is a geographic area under the political control and administration of a distant foreign power, typically exploited for economic, strategic, or settlement purposes.
-
B.
pre-colonial territory
A pre-colonial territory is a geographically defined area governed, used, or inhabited by indigenous or local societies before the imposition of foreign colonial rule and boundaries.
-
C.
former colonial settlement
A former colonial settlement is a community or territory originally established and governed by a foreign colonial power that has since transitioned to local or independent control, often retaining cultural, architectural, and institutional legacies of its colonial past.
-
D.
former British colonial land grant area
A former British colonial land grant area is a tract of land originally allocated by the British colonial administration—often to settlers, officials, or companies—under formal grant policies, whose boundaries and tenure patterns may still influence contemporary land ownership and governance.
-
E.
colonial district
A colonial district is an administrative subdivision established by a colonial power to govern, control, and organize a specific geographic area within its overseas territories.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.