Triple
T26301585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conquest of Tenerife |
E661572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the history of the Canary Islands |
C14498
|
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: event in the history of the Canary Islands Context triple: [Conquest of Tenerife, instanceOf, event in the history of the Canary Islands]
-
A.
event in the history of Spain
chosen
An event in the history of Spain is a significant occurrence or development within Spanish territory or involving Spanish actors that has contributed to shaping the nation’s political, social, cultural, or economic trajectory over time.
-
B.
event in the history of Portugal
An event in the history of Portugal is a significant occurrence or development, political, social, cultural, or economic, that took place within Portuguese territory or involved the Portuguese state and influenced its historical trajectory.
-
C.
event in Puerto Rico
An event in Puerto Rico is a scheduled occurrence—such as a festival, concert, conference, or community gathering—taking place within Puerto Rico at a specific time and location, often reflecting the island’s cultural, social, or professional activities.
-
D.
Hawaiian history event
A Hawaiian history event is a significant occurrence in the past of the Hawaiian Islands that shaped their political, cultural, social, or environmental development.
-
E.
event in the history of Uruguay
An event in the history of Uruguay is any significant occurrence or development, political, social, cultural, or economic, that has notably influenced the country’s historical trajectory.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:16 p.m.