Triple
T16668206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laguna Caliente |
E405037
|
entity |
| Predicate | surfaceActivity |
P67066
|
FINISHED |
| Object | frequent fumarolic activity |
—
|
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: frequent fumarolic activity | Statement: [Laguna Caliente, surfaceActivity, frequent fumarolic activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceActivity Context triple: [Laguna Caliente, surfaceActivity, frequent fumarolic activity]
-
A.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
B.
hasSurfaceActivity
chosen
Indicates that an entity exhibits measurable physical or chemical activity occurring at or on its surface.
-
C.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
-
D.
surfaceChange
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
E.
surfaceCurrent
Indicates that one entity is the prevailing flow or movement of a fluid (such as water or air) along the surface of another entity.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9e9a208190afab499897ce4361 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.