Triple
T9919290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayden Valley |
E185948
|
entity |
| Predicate | hasGeothermalInfluence |
P81464
|
FINISHED |
| Object | meadow soils |
—
|
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: meadow soils | Statement: [Hayden Valley, hasGeothermalInfluence, meadow soils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeothermalInfluence Context triple: [Hayden Valley, hasGeothermalInfluence, meadow soils]
-
A.
hasGeothermalPotential
Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
-
B.
hasGeothermalField
Indicates that an entity possesses, contains, or is associated with a geothermal field.
-
C.
hasHydrothermalActivity
chosen
Indicates that a location or geological feature exhibits hydrothermal activity, such as the circulation of heated water or fluids associated with geothermal processes.
-
D.
hasGeologicalActivity
Indicates that an entity exhibits or is associated with ongoing or past geological processes such as volcanism, tectonics, or seismic activity.
-
E.
hasGeologicalNature
Indicates that something possesses a specific geological character, composition, or formation type.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb5685a908190ab3e55b9bf9613f6 |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.