Triple
T4669175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Washington |
E102919
|
entity |
| Predicate | windSpeedRecordDate |
P58746
|
FINISHED |
| Object | April 12, 1934 |
—
|
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: April 12, 1934 | Statement: [Mount Washington, windSpeedRecordDate, April 12, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windSpeedRecordDate Context triple: [Mount Washington, windSpeedRecordDate, April 12, 1934]
-
A.
oneOfStrongestEverRecorded
Indicates that something belongs to a very small group of the most powerful or intense instances ever documented or measured.
-
B.
snowfallRecord
Indicates that a specific amount of snow has been measured or documented for a particular place and time.
-
C.
maximumGusts
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
-
D.
notableWeather
Indicates that a location experiences weather conditions that are significant, unusual, or noteworthy in some way.
-
E.
maximumRecordedTemperature
Indicates the highest temperature value that has been observed and recorded for a given entity or context.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd655719dc8190beb6942f343a0ae7 |
completed | March 20, 2026, 3:18 p.m. |
Created at: March 20, 2026, 1:15 p.m.