Triple
T8483588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Recordings, Vol. 1 |
E200777
|
entity |
| Predicate | containsVocalHarmonies |
P83531
|
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: [The New Recordings, Vol. 1, containsVocalHarmonies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsVocalHarmonies Context triple: [The New Recordings, Vol. 1, containsVocalHarmonies, true]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
-
C.
hasCallAndResponseVocals
Indicates that one entity produces vocalizations that are followed by corresponding or answering vocalizations from another entity.
-
D.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
E.
hasVocalDuet
Indicates that two entities perform or participate together in a vocal duet.
- F. None of above. chosen
Provenance (4 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53845e881909eeb32863c7aa942 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:12 p.m.