Triple
T6410724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Christina |
E127697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former Swedish colony settlement |
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 Swedish colony settlement Context triple: [Fort Christina, instanceOf, former Swedish colony settlement]
-
A.
Swedish colony
A Swedish colony is a territory outside Sweden that was settled, administered, and economically exploited under Swedish sovereignty during the period of its overseas expansion.
-
B.
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.
-
C.
former Dutch colony
A former Dutch colony is a territory that was once governed, administered, or significantly controlled by the Netherlands as part of its overseas colonial empire, but has since gained independence or been transferred to another sovereignty.
-
D.
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.
-
E.
historical province of Sweden
A historical province of Sweden is a traditional geographic and cultural region with historical significance, distinct identity, and often unique customs, which no longer serves as an administrative unit but remains important in cultural and regional contexts.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:41 p.m.