Triple
T1597115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorchester Company fishing outpost |
E34308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial settlement |
C213
|
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 settlement Context triple: [Dorchester Company fishing outpost, instanceOf, colonial settlement]
-
A.
agricultural colony
An agricultural colony is a settlement established primarily to cultivate land and produce food or raw materials, often organized around farming as its central economic and social activity.
-
B.
English colonial settlement
chosen
An English colonial settlement is a community established by England in foreign territories during the age of exploration and empire, serving as a base for resource extraction, trade, and cultural expansion.
-
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.
historical settlement
A historical settlement is a once-inhabited place of past human residence whose physical remains, records, and cultural traces provide evidence of earlier social, economic, and political life.
-
E.
Spanish colonial settlement
A Spanish colonial settlement is a community established by Spain in its overseas territories, typically organized around a central plaza with religious, administrative, and economic institutions to control, convert, and manage local populations and resources.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:27 p.m.