Triple
T7881122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Faithful |
E182979
|
entity |
| Predicate | hasEruptionSteam |
P2407
|
FINISHED |
| Object | visible steam plume during eruptions |
—
|
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: visible steam plume during eruptions | Statement: [Old Faithful, hasEruptionSteam, visible steam plume during eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEruptionSteam Context triple: [Old Faithful, hasEruptionSteam, visible steam plume during eruptions]
-
A.
hasFumaroles
chosen
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
B.
eruptionObserved
Indicates that an eruption event has been witnessed, detected, or recorded by an observer or observing system.
-
C.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
D.
hasVolcanicActivity
Indicates that the subject exhibits or is associated with ongoing or past volcanic processes, such as eruptions, lava flows, or related geothermal activity.
-
E.
erupted
Indicates that a volcano or similar geological feature suddenly expelled lava, ash, gas, or other material in a violent outburst.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39bffbc481908e868ab98a38e10a |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.