Triple
T38165906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Louise |
E953142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European trading post |
C54696
|
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: European trading post Context triple: [Fort Louise, instanceOf, European trading post]
-
A.
Portuguese trading post
A Portuguese trading post is a fortified coastal or riverside settlement established by Portugal during the Age of Exploration to control trade routes, facilitate commerce, and project imperial influence.
-
B.
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.
-
C.
colonial-era trading outpost
chosen
A colonial-era trading outpost is a remote settlement established by an imperial power to facilitate the exchange of goods, resources, and information between the colonizing nation and local populations, often serving as a strategic hub for commerce, governance, and cultural contact.
-
D.
medieval trading colony
A medieval trading colony is a distant settlement established and controlled by a city or state to facilitate long-distance commerce, resource extraction, and cultural exchange through permanent mercantile presence.
-
E.
maritime trading centre
A maritime trading centre is a coastal hub where goods, services, and information are exchanged via sea routes, integrating port infrastructure, commercial activities, and logistics networks to facilitate regional and international trade.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.