Triple
T9300406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aconcagua summit area |
E223743
|
entity |
| Predicate | extremeWindSpeed |
P45372
|
FINISHED |
| Object | can exceed 100 km/h |
—
|
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: can exceed 100 km/h | Statement: [Aconcagua summit area, extremeWindSpeed, can exceed 100 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extremeWindSpeed Context triple: [Aconcagua summit area, extremeWindSpeed, can exceed 100 km/h]
-
A.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
B.
maximumSustainedWinds
Indicates the highest wind speed that is maintained continuously over a specified averaging period, rather than in brief gusts.
-
C.
maximumGusts
chosen
Indicates the relationship where a recorded wind gust value represents the highest (maximum) gust observed within a specified time or context.
-
D.
windSpeedRecordDate
Indicates the date on which a particular wind speed measurement or record was observed or recorded.
-
E.
hasExtremeWeatherCharacteristic
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d070c881908bed41aada6f85ae |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.