Triple
T3533832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagasaki trading post |
E74722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese trading post |
C12883
|
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 trading post Context triple: [Nagasaki trading post, instanceOf, Portuguese trading post]
-
A.
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.
-
B.
Portuguese overseas possession
A Portuguese overseas possession is a territory outside Europe that was under the political, economic, and administrative control of the Kingdom (and later Republic) of Portugal as part of its colonial empire.
-
C.
Dutch colony
A Dutch colony is a territory politically and economically controlled by the Netherlands, established primarily for trade, resource extraction, and strategic influence during the era of European imperial expansion.
-
D.
maritime kingdom
A maritime kingdom is a sovereign state whose power, economy, and culture are primarily based on seafaring, naval strength, and control of important sea routes and coastal territories.
-
E.
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.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:19 p.m.