Triple
T9647071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pistol River |
E233225
|
entity |
| Predicate | hasWindCondition |
P74831
|
FINISHED |
| Object | strong coastal winds suitable for windsurfing |
—
|
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: strong coastal winds suitable for windsurfing | Statement: [Pistol River, hasWindCondition, strong coastal winds suitable for windsurfing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWindCondition Context triple: [Pistol River, hasWindCondition, strong coastal winds suitable for windsurfing]
-
A.
hasWindPattern
Indicates that one entity exhibits, is characterized by, or is associated with a particular pattern of wind behavior.
-
B.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
C.
usedWhenWindFrom
Indicates that something is employed or activated under conditions where the wind is coming from a specified direction.
-
D.
windCharacteristics
chosen
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
E.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b826ff08190a972bdef84405f08 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.