Triple
T20015062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivo per lei |
E494694
|
entity |
| Predicate | hasDuetStructure |
P9649
|
FINISHED |
| Object | male-female vocal parts |
—
|
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: male-female vocal parts | Statement: [Vivo per lei, hasDuetStructure, male-female vocal parts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDuetStructure Context triple: [Vivo per lei, hasDuetStructure, male-female vocal parts]
-
A.
hasVocalDuet
chosen
Indicates that two entities perform or participate together in a vocal duet.
-
B.
isDoubleSong
Indicates that one song is a duplicate or alternate version of another song, such as a second take, remix, or re-recording.
-
C.
hasNotablePerformerDuo
Indicates that the subject has a notable performing duo associated with it, such as a well-known pair of artists or entertainers who perform together.
-
D.
hasTwoTracks
Indicates that the subject possesses or is associated with exactly two distinct tracks or pathways.
-
E.
hasVerseChorusStructure
Indicates that something, typically a musical composition, is organized using a recurring pattern of verses and choruses.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623bba1881908440c92f08729ec1 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.