Triple
T21419394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scenes from the Southside |
E528394
|
entity |
| Predicate | includesVocalStyle |
P135747
|
FINISHED |
| Object | male lead 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: male lead vocals | Statement: [Scenes from the Southside, includesVocalStyle, male lead vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVocalStyle Context triple: [Scenes from the Southside, includesVocalStyle, male lead vocals]
-
A.
hasMusicalVocalType
chosen
Indicates that an entity is associated with a specific type or classification of singing voice.
-
B.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
E.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2ccddc08190b4f66fa6ccda41e2 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:47 p.m.