Triple
T6780197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort de Kock |
E155659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former colonial garrison town |
C12591
|
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: former colonial garrison town Context triple: [Fort de Kock, instanceOf, former colonial garrison town]
-
A.
former colonial settlement
chosen
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.
-
B.
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.
-
C.
former sugar plantation town
A former sugar plantation town is a community whose origins, layout, and social fabric were shaped by historical sugar cultivation and processing, but which has since transitioned away from plantation-based agriculture as its primary economic foundation.
-
D.
former town
A former town is a once-recognized populated settlement that has lost its official town status due to abandonment, depopulation, annexation, or administrative reorganization.
-
E.
former British colony
A former British colony is a territory that was once governed or administered by the British Empire but has since gained independence or undergone a change in political status.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.