Triple
T5469189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelso Dunes |
E122787
|
entity |
| Predicate | soundPhenomenon |
P8089
|
FINISHED |
| Object | booming sound produced by avalanching sand |
—
|
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: booming sound produced by avalanching sand | Statement: [Kelso Dunes, soundPhenomenon, booming sound produced by avalanching sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundPhenomenon Context triple: [Kelso Dunes, soundPhenomenon, booming sound produced by avalanching sand]
-
A.
soundEffects
Indicates that one entity produces, contains, or is associated with sound effects used to accompany or enhance another entity.
-
B.
soundAmplification
Indicates that one entity increases the loudness or intensity of another entity’s sound.
-
C.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
-
D.
soundCharacter
chosen
Indicates a relationship where one entity specifies the quality, style, or distinguishing characteristics of a sound produced or perceived in another entity.
-
E.
followsSoundOf
Indicates that one entity moves or directs its attention by tracking the source or direction of a sound produced by another entity.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.