Triple
T38202693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish reconquest of New Mexico |
E1009110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial campaign |
C66271
|
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: colonial campaign Context triple: [Spanish reconquest of New Mexico, instanceOf, colonial campaign]
-
A.
colonization campaign
A colonization campaign is an organized, often state- or corporate-led effort to establish control, settlement, and resource exploitation in a new territory, typically involving migration, infrastructure development, and cultural or political domination over existing populations.
-
B.
Dutch colonial military campaign
A Dutch colonial military campaign is an organized series of armed operations conducted by the Netherlands to conquer, pacify, or control territories and populations within its overseas empire.
-
C.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
D.
Mughal campaign
A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
-
E.
British colonial military operation
A British colonial military operation is a coordinated campaign conducted by British armed forces to establish, maintain, or expand control over territories within the British Empire, often involving combat, occupation, and enforcement of imperial policies.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.