Triple
T24962848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenerife volcanic system |
E624654
|
entity |
| Predicate | islandBuildingRole |
P124656
|
FINISHED |
| Object | main builder of Tenerife island |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: main builder of Tenerife island | Statement: [Tenerife volcanic system, islandBuildingRole, main builder of Tenerife island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: islandBuildingRole Context triple: [Tenerife volcanic system, islandBuildingRole, main builder of Tenerife island]
-
A.
islandFormationRole
chosen
Indicates the role or contribution an entity has in the process by which an island is formed.
-
B.
roleOnIsland
Indicates the specific function, position, or responsibility an entity holds within the context of an island.
-
C.
hasBuildingOnIsland
Indicates that a particular building is located on or associated with a specific island.
-
D.
isOnIslandFormedBy
Indicates that one entity is located on an island that has been created or formed by another entity or process.
-
E.
islandType
Indicates the specific classification or category of an island based on its characteristics or formation.
- F. None of above.
Provenance (3 batches)
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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:59 a.m.