Triple
T12791449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patagonian steppe |
E305773
|
entity |
| Predicate | windDirection |
P74831
|
FINISHED |
| Object | predominantly westerly |
—
|
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: predominantly westerly | Statement: [Patagonian steppe, windDirection, predominantly westerly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: windDirection Context triple: [Patagonian steppe, windDirection, predominantly westerly]
-
A.
windSpeed
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
B.
windCharacteristics
chosen
Indicates the specific properties or qualities that describe the behavior and nature of the wind in a given context.
-
C.
windDirectionAtLandfall
Indicates the direction from which the wind is blowing at the moment and location where a storm makes landfall.
-
D.
prevailingSurfaceWinds
Indicates the typical or most frequently occurring wind direction and speed that dominate at a given location over a specified period.
-
E.
waveDirection
Indicates the direction in which a wave is propagating or traveling relative to a reference frame.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6b55248190ab938e69eb263612 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.