Triple
T20622404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doyle Wolfgang von Frankenstein |
E506731
|
entity |
| Predicate | vocalParticipation |
P44280
|
FINISHED |
| Object | backing vocals in Misfits |
—
|
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: backing vocals in Misfits | Statement: [Doyle Wolfgang von Frankenstein, vocalParticipation, backing vocals in Misfits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalParticipation Context triple: [Doyle Wolfgang von Frankenstein, vocalParticipation, backing vocals in Misfits]
-
A.
hasVocalPartInMovement
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
-
B.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
C.
vocalRequirement
Indicates that a particular action, role, or participation involves a specified need or condition related to vocal use, such as speaking or singing.
-
D.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
- 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_69e0b4bc90988190ac360aaf645efc1d |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe25c208190af057bcd1aa6219d |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:42 a.m.