Triple
T28754088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcán Teneguía |
E731617
|
entity |
| Predicate | hasLavaFlowsEnteringSea |
P17576
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Volcán Teneguía, hasLavaFlowsEnteringSea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLavaFlowsEnteringSea Context triple: [Volcán Teneguía, hasLavaFlowsEnteringSea, true]
-
A.
hasLavaFlow
chosen
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
B.
hasHydrothermalActivity
Indicates that a location or geological feature exhibits hydrothermal activity, such as the circulation of heated water or fluids associated with geothermal processes.
-
C.
hasVolcanicLake
Indicates that an entity contains or features a lake formed in or directly associated with volcanic activity.
-
D.
areaCoveredByLava
Indicates that a specified region or surface is (or was) physically covered by lava.
-
E.
hasLavaDomes
Indicates that the subject volcano possesses one or more lava domes as part of its structure or eruptive features.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 6:08 a.m.