Triple
T17145772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Geldria |
E416087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial stronghold |
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 stronghold Context triple: [Fort Geldria, instanceOf, colonial stronghold]
-
A.
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.
-
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 empire
A colonial empire is a political and economic system in which a dominant state controls and exploits distant territories and their populations, typically through settlement, resource extraction, and imposed governance.
-
D.
Dutch trading post
A Dutch trading post is a commercial outpost established by the Dutch, primarily during the 17th and 18th centuries, to facilitate trade, resource extraction, and colonial administration in foreign 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. 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:36 a.m.