Triple
T12275264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Can't Get Next to You |
E292571
|
entity |
| Predicate | vocalArrangementFeatures |
P37619
|
FINISHED |
| Object | multiple lead vocalists |
—
|
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: multiple lead vocalists | Statement: [I Can't Get Next to You, vocalArrangementFeatures, multiple lead vocalists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalArrangementFeatures Context triple: [I Can't Get Next to You, vocalArrangementFeatures, multiple lead vocalists]
-
A.
vocalArrangement
chosen
Indicates the specific way vocal parts or voices are organized, structured, and combined within a musical work or performance.
-
B.
featuresVocalEnsemble
Indicates that something includes or presents a group of vocal performers singing together.
-
C.
vocalForm
Indicates the specific vocal or phonetic form in which something (such as a word, sound, or utterance) is expressed.
-
D.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
E.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.