Triple
T22483824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grateful Dead Movie Soundtrack |
E555831
|
entity |
| Predicate | hasLiveSoundMix |
P144170
|
FINISHED |
| Object | concert soundboard and audience sources |
—
|
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: concert soundboard and audience sources | Statement: [The Grateful Dead Movie Soundtrack, hasLiveSoundMix, concert soundboard and audience sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveSoundMix Context triple: [The Grateful Dead Movie Soundtrack, hasLiveSoundMix, concert soundboard and audience sources]
-
A.
hasSoundMix
chosen
Indicates that one entity uses, features, or is associated with a particular sound mix configuration or audio mixing format.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
hasSoundSystem
Indicates that an entity is equipped with or includes a sound system as one of its features.
-
D.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
E.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3b03d881909e286a124c1a2b1c |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.