Triple
T5926643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santiago de Nueva Extremadura |
E131828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish colonial foundation |
C3699
|
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 colonial foundation Context triple: [Santiago de Nueva Extremadura, instanceOf, Spanish colonial foundation]
-
A.
Spanish colonial settlement
chosen
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.
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.
-
C.
Spanish colonial governor
A Spanish colonial governor was the crown-appointed official responsible for administering, defending, and representing royal authority in a designated overseas territory of the Spanish Empire.
-
D.
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.
-
E.
Spanish Colonial adobe church
A Spanish Colonial adobe church is a religious structure characterized by thick earthen walls, simple rectilinear forms, and modest ornamentation that blend indigenous building techniques with Spanish ecclesiastical design.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4 p.m.