Triple
T26301694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1949 Cumbre Vieja eruption |
E661574
|
entity |
| Predicate | createdCone |
P173343
|
FINISHED |
| Object | Duraznero vent |
—
|
NE NERFINISHED |
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: Duraznero vent | Statement: [1949 Cumbre Vieja eruption, createdCone, Duraznero vent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdCone Context triple: [1949 Cumbre Vieja eruption, createdCone, Duraznero vent]
-
A.
hasCone
Indicates that one entity possesses, is equipped with, or is characterized by a cone or cone-shaped component.
-
B.
coneType
Indicates the specific category or style of cone associated with an entity (e.g., type, shape, or design of the cone).
-
C.
hasConeType
Indicates that an entity possesses or is associated with a specific type or category of cone.
-
D.
isYoungerConeOf
Indicates that one cone (in a hierarchical or branching structure) is derived later or is considered temporally or developmentally younger than another cone.
-
E.
hasCones
Indicates that an entity possesses or is characterized by cones (e.g., cone-shaped structures or cone-bearing features).
- F. None of above. chosen
Provenance (4 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 26, 2026, 10:16 p.m.