Triple
T24168060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whistling Death |
E599047
|
entity |
| Predicate | hasDistinctiveSound |
P144957
|
FINISHED |
| Object | whistling noise during dives and high-speed passes |
—
|
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: whistling noise during dives and high-speed passes | Statement: [Whistling Death, hasDistinctiveSound, whistling noise during dives and high-speed passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctiveSound Context triple: [Whistling Death, hasDistinctiveSound, whistling noise during dives and high-speed passes]
-
A.
notableSoundCharacteristic
chosen
Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
-
B.
hasCatchySound
Indicates that something possesses an appealing, memorable, or attractive auditory quality.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
hasDistinctLetterForSound
Indicates that a particular sound is represented by its own unique letter, distinct from other sounds in the writing system.
-
E.
hasHeavierSoundThan
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.