Triple
T32031164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beowawe geothermal area |
E817961
|
entity |
| Predicate | temperatureClassification |
P100818
|
FINISHED |
| Object | high-temperature geothermal field |
—
|
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: high-temperature geothermal field | Statement: [Beowawe geothermal area, temperatureClassification, high-temperature geothermal field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temperatureClassification Context triple: [Beowawe geothermal area, temperatureClassification, high-temperature geothermal field]
-
A.
hasTemperatureCategory
chosen
Indicates that an entity is associated with a specific qualitative temperature classification (e.g., hot, cold, warm).
-
B.
temperatureConditions
Indicates the specific thermal or weather-related temperature state or range affecting an entity or situation.
-
C.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
D.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
E.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b494f66c8190ada271cdb0a21195 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:18 a.m.