Triple
T14033996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vosporo |
E337662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Genoese colonial settlement |
C12480
|
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: Genoese colonial settlement Context triple: [Vosporo, instanceOf, Genoese colonial settlement]
-
A.
Genoese colony
chosen
A Genoese colony was a territorial possession or trading outpost established and administered by the Republic of Genoa to control maritime commerce, strategic ports, and regional influence across the Mediterranean and Black Sea.
-
B.
Phoenician colony
A Phoenician colony is a settlement established by the ancient maritime Phoenician civilization along foreign coasts for trade, resource extraction, and cultural expansion while maintaining ties to its founding city.
-
C.
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.
-
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.
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.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.