Triple
T5333814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So in Love with You |
E123374
|
entity |
| Predicate | hasVocalArrangement |
P37619
|
FINISHED |
| Object | harmonized male 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: harmonized male vocals | Statement: [So in Love with You, hasVocalArrangement, harmonized male vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalArrangement Context triple: [So in Love with You, hasVocalArrangement, harmonized male vocals]
-
A.
vocalArrangement
chosen
Indicates the specific way vocal parts or voices are organized, structured, and combined within a musical work or performance.
-
B.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
C.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
-
E.
hasVocalDuet
Indicates that two entities perform or participate together in a vocal duet.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ae52c08190968a5567b7e6b794 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.