Triple
T35776214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Layover |
E1034297
|
entity |
| Predicate | hasPrimaryVocalTexture |
P206045
|
FINISHED |
| Object | group harmonies |
—
|
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: group harmonies | Statement: [Layover, hasPrimaryVocalTexture, group harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryVocalTexture Context triple: [Layover, hasPrimaryVocalTexture, group harmonies]
-
A.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
B.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
C.
hasSecondaryVocalStyle
Indicates that an entity (typically a performer or recording) employs an additional, non-primary vocal style alongside its main vocal style.
-
D.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
E.
hasMainVocals
Indicates that the specified entity performs the primary or lead vocal part in a musical work or performance.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.