Triple
T17096678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pánfilo de Narváez expedition of 1528 |
E414867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | failed colonization attempt |
C17259
|
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: failed colonization attempt Context triple: [Pánfilo de Narváez expedition of 1528, instanceOf, failed colonization attempt]
-
A.
failed colony
chosen
A failed colony is a settlement attempt that has collapsed or been abandoned due to insurmountable environmental, social, economic, or political challenges, leaving little or no sustainable population or infrastructure behind.
-
B.
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.
-
C.
failed acquisition attempt
A failed acquisition attempt is an incomplete or unsuccessful effort by one entity to purchase or take control of another, which does not result in a finalized transaction.
-
D.
failed space mission
A failed space mission is an attempted journey or operation beyond Earth's atmosphere that does not achieve its primary objectives due to technical, human, environmental, or organizational factors.
-
E.
failed coup
A failed coup is an unsuccessful attempt by a group—often including military or political insiders—to illegally seize state power, which is thwarted before consolidating control.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.