Triple
T14656751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red, Black & Green |
E344129
|
entity |
| Predicate | hasVocalElements |
P25705
|
FINISHED |
| Object | sung vocals |
—
|
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: sung vocals | Statement: [Red, Black & Green, hasVocalElements, sung vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalElements Context triple: [Red, Black & Green, hasVocalElements, sung vocals]
-
A.
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.
-
B.
hasVocalLanguageMix
Indicates that an entity’s vocal communication combines multiple languages or language varieties within its speech.
-
C.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
-
D.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
E.
hasVocalProcessing
Indicates that an entity’s vocal audio has been altered or enhanced through some form of signal processing.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51a562c819098971447db4b29f7 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.