Triple
T9919232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norris Geyser Basin |
E185947
|
entity |
| Predicate | hasHighestTemperature |
P91147
|
FINISHED |
| Object | among major Yellowstone geyser basins |
—
|
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: among major Yellowstone geyser basins | Statement: [Norris Geyser Basin, hasHighestTemperature, among major Yellowstone geyser basins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestTemperature Context triple: [Norris Geyser Basin, hasHighestTemperature, among major Yellowstone geyser basins]
-
A.
maximumRecordedTemperature
Indicates the highest temperature value that has been observed and recorded for a given entity or context.
-
B.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
C.
recordHighTemperatureLocation
Indicates the location where the highest recorded temperature occurred.
-
D.
hasTemperature
Indicates that an entity possesses or is characterized by a specific temperature value.
-
E.
isHotterThan
Indicates that one entity has a higher temperature than another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:42 p.m.