Triple
T6706899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Yasur |
E153028
|
entity |
| Predicate | hasLavaLake |
P72552
|
FINISHED |
| Object | intermittent or transient lava lake activity reported |
—
|
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: intermittent or transient lava lake activity reported | Statement: [Mount Yasur, hasLavaLake, intermittent or transient lava lake activity reported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLavaLake Context triple: [Mount Yasur, hasLavaLake, intermittent or transient lava lake activity reported]
-
A.
hasLowerLake
Indicates that one lake is situated at a lower elevation or downstream position relative to another lake.
-
B.
hasRapids
Indicates that a body of water contains sections of fast-flowing, turbulent water known as rapids.
-
C.
hasLoch
Indicates that one entity possesses, contains, or features a loch (lake or sea inlet) as part of its characteristics or composition.
-
D.
hasLavaFlow
Indicates that one entity exhibits, contains, or is associated with a flow of lava originating from volcanic activity.
-
E.
hasLakeGroup
Indicates that an entity possesses, contains, or is associated with a specific group or collection of lakes.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:06 p.m.