Triple
T29155479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peters Point trading post |
E739026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era trading outpost |
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: colonial-era trading outpost Context triple: [Peters Point trading post, instanceOf, colonial-era trading outpost]
-
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.
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.
-
C.
colonial-era trade corridor
A colonial-era trade corridor is a strategically established route or network used during colonial times to transport goods, people, and resources between colonies and imperial centers, shaping economic patterns and cultural exchanges.
-
D.
colonial stronghold
A colonial stronghold is a heavily fortified settlement or military outpost established by a colonizing power to secure control, protect resources, and project authority over a foreign territory.
-
E.
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.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:44 a.m.