Triple
T5605150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Du |
E147214
|
entity |
| Predicate | commonWeather |
P2044
|
FINISHED |
| Object | high winds |
—
|
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: high winds | Statement: [Corn Du, commonWeather, high winds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonWeather Context triple: [Corn Du, commonWeather, high winds]
-
A.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
-
B.
weatherRole
Indicates a role or function that an entity has in relation to weather conditions or weather-related phenomena.
-
C.
hasWeather
chosen
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
-
D.
canProvideWeatherInformation
Indicates that an entity has the capability to supply or answer queries about weather-related data or conditions.
-
E.
weatherConsideration
Indicates that certain conditions, decisions, or actions take into account or are influenced by the current or expected weather.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fa4b0881909fdbb8ea38eeb5e3 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.