Triple
T20622301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerry Only |
E506728
|
entity |
| Predicate | notableVocalRole |
P24740
|
FINISHED |
| Object | lead vocals for Misfits in later lineups |
—
|
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: lead vocals for Misfits in later lineups | Statement: [Jerry Only, notableVocalRole, lead vocals for Misfits in later lineups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVocalRole Context triple: [Jerry Only, notableVocalRole, lead vocals for Misfits in later lineups]
-
A.
notableLyricSopranoRole
Indicates that the subject is notably recognized for performing the specified lyric soprano role.
-
B.
notableSopranoRole
Indicates that the object is a soprano role for which the subject is particularly well known or distinguished.
-
C.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
D.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
E.
notableCharacterVoiced
Indicates that a notable character is voiced or performed by a specific voice actor or performer.
- 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.