Triple
T3227743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mussoorie |
E67662
|
entity |
| Predicate | summerTemperatureRange |
P21374
|
FINISHED |
| Object | about 15–25 °C |
—
|
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: about 15–25 °C | Statement: [Mussoorie, summerTemperatureRange, about 15–25 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerTemperatureRange Context triple: [Mussoorie, summerTemperatureRange, about 15–25 °C]
-
A.
summerHighTemperaturesOftenExceed
Indicates that during the summer season, the high temperatures in a given location frequently surpass a specified threshold.
-
B.
summerClimate
chosen
Indicates the typical weather conditions or characteristics that prevail in a place during the summer season.
-
C.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
D.
averageTemperature
Indicates the typical or mean temperature value associated with an entity over a specified period or context.
-
E.
averageMaxTemperatureWarmestMonth
Indicates the highest average temperature recorded in the warmest month of a given time period or location.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb5e67c819082070d108d3613ba |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0dc2248190a38c40f4e06cd41c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.