Triple
T37928603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockout |
E946154
|
entity |
| Predicate | hasWeatherEffect |
P134282
|
FINISHED |
| Object | falling snow |
—
|
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: falling snow | Statement: [Lockout, hasWeatherEffect, falling snow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeatherEffect Context triple: [Lockout, hasWeatherEffect, falling snow]
-
A.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
-
B.
hasSignificantWeatherInfluence
Indicates that one entity exerts a substantial impact on the weather conditions or patterns experienced by another entity or region.
-
C.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
D.
hasWeatherContext
chosen
Indicates that something is associated with, influenced by, or described in terms of specific weather conditions or patterns.
-
E.
weatherCapability
Indicates that an entity has the ability or functionality to provide, process, or otherwise handle weather-related information or services.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.