Triple
T26413146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teneguía |
E664013
|
entity |
| Predicate | eruptionLavaFlows |
P105661
|
FINISHED |
| Object | lava flows reached the sea in 1971 |
—
|
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: lava flows reached the sea in 1971 | Statement: [Teneguía, eruptionLavaFlows, lava flows reached the sea in 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionLavaFlows Context triple: [Teneguía, eruptionLavaFlows, lava flows reached the sea in 1971]
-
A.
eruptionVolcano
Indicates that a volcanic eruption event is occurring at or is associated with a specific volcano.
-
B.
eruptionPhenomena
chosen
Indicates the specific observable events or manifestations that occur during a volcanic eruption.
-
C.
eruptionFocus
Indicates that an eruption event is centered on, originates from, or is primarily associated with a particular focal location or feature.
-
D.
eruptionEvidence
Indicates that there is observable or documented evidence supporting the occurrence of a volcanic eruption.
-
E.
typicalLavaType
Indicates the usual or characteristic type of lava associated with a given volcanic feature, eruption, or context.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11:39 p.m.