Triple
T2183420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan Ruiz de Apodaca |
E49097
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | viceroy of New Spain |
C4445
|
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: viceroy of New Spain Context triple: [Juan Ruiz de Apodaca, instanceOf, viceroy of New Spain]
-
A.
Spanish colonial governor
chosen
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.
-
B.
tlatoani of Tenochtitlan
The tlatoani of Tenochtitlan was the supreme ruler and political, military, and religious leader of the Mexica (Aztec) capital city-state, governing its affairs and representing its authority within the broader Aztec Empire.
-
C.
Supreme Director of Chile
The Supreme Director of Chile was the title given to the chief executive authority who governed Chile during its early republican period, holding broad political and military powers before the establishment of a stable constitutional presidency.
-
D.
Aztec ruler
An Aztec ruler was the supreme political, military, and religious leader of the Aztec Empire, responsible for governing the state, leading armies, overseeing tribute, and serving as an intermediary with the gods.
-
E.
Governor-General of the Habsburg Netherlands
The Governor-General of the Habsburg Netherlands was the monarch’s chief representative who governed the provinces on behalf of the Habsburg ruler, overseeing administration, military affairs, and the implementation of imperial policy.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:45 p.m.