Triple
T27171609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Wa-Da-Da (Invasion) (Dub) |
E682927
|
entity |
| Predicate | audioMixType |
P144170
|
FINISHED |
| Object | dub version |
—
|
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: dub version | Statement: [Black Wa-Da-Da (Invasion) (Dub), audioMixType, dub version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioMixType Context triple: [Black Wa-Da-Da (Invasion) (Dub), audioMixType, dub version]
-
A.
mixType
Indicates that one entity is combined or blended with another in a particular manner or category of mixing.
-
B.
hasSoundMix
chosen
Indicates that one entity uses, features, or is associated with a particular sound mix configuration or audio mixing format.
-
C.
channelMixing
Indicates a relationship where content, signals, or resources from multiple channels are combined, blended, or interchanged into a unified or altered output.
-
D.
mixingMethod
Indicates the technique or process used to combine multiple components or substances into a uniform mixture.
-
E.
audioChannelType
Indicates the specific role or configuration of an audio channel within a multi-channel audio setup (e.g., left, right, center, surround).
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62547f92c8190818a05f9836a0843 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:24 a.m.