Triple
T30444745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Ana winds |
E774545
|
entity |
| Predicate | blowToward |
P143482
|
FINISHED |
| Object | coastal Southern California |
—
|
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: coastal Southern California | Statement: [Santa Ana winds, blowToward, coastal Southern California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blowToward Context triple: [Santa Ana winds, blowToward, coastal Southern California]
-
A.
blows
chosen
Indicates that one entity forcefully expels air or creates a current of air directed toward or acting upon another entity.
-
B.
blowsAcross
Indicates that something (typically wind, air, or a current) moves across or over another entity or area, passing from one side or region to another.
-
C.
blowsOver
Indicates that one entity is toppled or knocked down by the force or movement of another entity.
-
D.
blowsDownSlopeOf
Indicates that something (typically wind or air) moves or exerts force downward along the incline or gradient of a slope relative to another entity.
-
E.
blowCharacteristics
Indicates the specific qualities or attributes associated with a blow, such as its force, direction, or manner.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686be108c8190a8ec98dc286ab03b |
completed | May 2, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:08 p.m.