Triple
T26059068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viceroyalty of the Río de la Plata |
E657205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish colony |
C4345
|
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: Spanish colony Context triple: [Viceroyalty of the Río de la Plata, instanceOf, Spanish colony]
-
A.
Spanish colonial settlement
A Spanish colonial settlement is a community established by Spain in its overseas territories, typically organized around a central plaza with religious, administrative, and economic institutions to control, convert, and manage local populations and resources.
-
B.
viceroyalty of the Spanish Empire
A viceroyalty of the Spanish Empire was a major territorial and administrative division governed by a viceroy who represented the Spanish monarch and exercised political, military, and economic authority over colonial lands.
-
C.
Spanish colonial institution
A Spanish colonial institution is an organization or system established by the Spanish Empire to administer, control, and exploit its overseas territories through political, economic, religious, and social structures.
-
D.
former Spanish possession
chosen
A former Spanish possession is a territory or colony that was once under the sovereignty or administrative control of the Spanish Crown but is no longer governed by Spain.
-
E.
Spanish colonial fortification
A Spanish colonial fortification is a military structure built by the Spanish Empire in its overseas territories to defend strategic ports, settlements, and trade routes from rival powers and local resistance.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:14 p.m.