Triple
T23550571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gods' Dice |
E578028
|
entity |
| Predicate | hasSoundCharacteristics |
P48651
|
FINISHED |
| Object | immersive sound design |
—
|
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: immersive sound design | Statement: [Gods' Dice, hasSoundCharacteristics, immersive sound design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundCharacteristics Context triple: [Gods' Dice, hasSoundCharacteristics, immersive sound design]
-
A.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
B.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
C.
hasMusicCharacteristic
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
D.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
E.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aece662081909022e7a29f966ca3 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.