Triple
T13035564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Groningen (Spanish-aligned) |
E326552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish-aligned polity |
C32372
|
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-aligned polity Context triple: [City of Groningen (Spanish-aligned), instanceOf, Spanish-aligned polity]
-
A.
Iberian polity
An Iberian polity is a political entity—such as a kingdom, state, or autonomous region—located on or historically associated with the Iberian Peninsula, encompassing parts of modern Spain, Portugal, Andorra, Gibraltar, and adjacent territories.
-
B.
former Spanish possession
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.
-
C.
Spanish exclave
A Spanish exclave is a geographically separated portion of Spain’s sovereign territory that is entirely surrounded by foreign land or international waters and not contiguous with the Spanish mainland.
-
D.
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.
-
E.
constituent territory of Spain
A constituent territory of Spain is a primary political-administrative unit, such as an autonomous community or city, that forms part of the Spanish state with defined powers and governance structures under the Spanish Constitution.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:55 p.m.