Triple
T24695609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cossack ostrog (fortress) |
E611575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial outpost |
C38605
|
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 outpost Context triple: [Cossack ostrog (fortress), instanceOf, colonial outpost]
-
A.
colonial stronghold
chosen
A colonial stronghold is a heavily fortified settlement or military outpost established by a colonizing power to secure control, protect resources, and project authority over a foreign territory.
-
B.
colonial territory
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.
-
C.
colonial city
A colonial city is an urban settlement established or significantly reshaped by a foreign colonial power, typically characterized by imposed administrative, economic, and cultural structures that reflect the colonizer’s interests more than those of the indigenous population.
-
D.
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.
-
E.
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.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 3:21 a.m.