Triple
T13705115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese India Armadas |
E328619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese maritime enterprise |
C14737
|
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: Portuguese maritime enterprise Context triple: [Portuguese India Armadas, instanceOf, Portuguese maritime enterprise]
-
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.
British slave-trading company
A British slave-trading company is a commercial enterprise, chartered or based in Britain, that organized, financed, and profited from the capture, transport, and sale of enslaved Africans across the Atlantic.
-
C.
Portuguese navigator
A Portuguese navigator is an expert seafarer from Portugal skilled in charting courses, exploring unknown waters, and guiding ships safely across long ocean voyages.
-
D.
transoceanic trade network
A transoceanic trade network is a system of interconnected maritime routes, ports, merchants, and institutions that facilitate the large-scale exchange of goods, people, capital, and ideas across oceans between distant regions of the world.
-
E.
chartered trading company
chosen
A chartered trading company is a business organization granted exclusive rights and privileges by a government charter to conduct trade, often in specific regions or commodities, typically during the early modern period.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.