Triple
T30965913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sespe Hot Springs |
E788955
|
entity |
| Predicate | hasMaximumTemperature |
P91147
|
FINISHED |
| Object | approximately 190 °F |
—
|
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: approximately 190 °F | Statement: [Sespe Hot Springs, hasMaximumTemperature, approximately 190 °F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumTemperature Context triple: [Sespe Hot Springs, hasMaximumTemperature, approximately 190 °F]
-
A.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
B.
hasMinTemperature
Indicates that something possesses or is associated with a specified minimum temperature value.
-
C.
hasTemperatureCriterion
Indicates that something is associated with a specific temperature-based condition or requirement that must be met.
-
D.
hasCriticalTemperature
Indicates that an entity possesses a specific temperature value at which a critical physical change or phase transition occurs.
-
E.
hasHighestTemperature
chosen
Indicates that the referenced entity possesses the greatest temperature value compared to all other relevant entities in the given context.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: April 29, 2026, 8:54 p.m.