Triple
T20266677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying in a Blue Dream |
E498987
|
entity |
| Predicate | includesVocalTracks |
P25705
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Flying in a Blue Dream, includesVocalTracks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVocalTracks Context triple: [Flying in a Blue Dream, includesVocalTracks, true]
-
A.
usesMultiTrackVocals
Indicates that the subject employs multiple separately recorded vocal tracks layered together in the audio or performance.
-
B.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
-
C.
includesScratchVocalsFrom
Indicates that one audio recording or track contains scratch (temporary or demo) vocal parts taken from another recording or session.
-
D.
hasVocals
chosen
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
E.
containsVocalHarmonies
Indicates that the subject includes multiple vocal parts sung together in harmony.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e674d001f081908910eedd262ae13a |
completed | April 20, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.