Triple
T16255871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karlovy Vary |
E394624
|
entity |
| Predicate | hasHighestSpringTemperatureApprox |
P122372
|
FINISHED |
| Object | 72 °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: 72 °C | Statement: [Karlovy Vary, hasHighestSpringTemperatureApprox, 72 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestSpringTemperatureApprox Context triple: [Karlovy Vary, hasHighestSpringTemperatureApprox, 72 °C]
-
A.
hasHighestTemperature
Indicates that the referenced entity possesses the greatest temperature value compared to all other relevant entities in the given context.
-
B.
hasAverageSpringTemperature
Indicates that an entity is associated with a specific average temperature value measured over the spring season.
-
C.
maximumRecordedTemperature
Indicates the highest temperature value that has been observed and recorded for a given entity or context.
-
D.
averageAnnualHighTemperature
Indicates the typical yearly mean of the highest daily temperatures recorded for a given location or entity.
-
E.
averageWarmestMonth
Indicates the relationship between a place and the month in which its long-term average temperature is highest.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459a48f081909c76b38741b8f04e |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.