Triple
T18820333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classix Nouveaux |
E460245
|
entity |
| Predicate | roleOfSalSolo |
P24740
|
FINISHED |
| Object | lead vocalist |
—
|
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 vocalist | Statement: [Classix Nouveaux, roleOfSalSolo, lead vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfSalSolo Context triple: [Classix Nouveaux, roleOfSalSolo, lead vocalist]
-
A.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
B.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
C.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
D.
roleInGuitarHero
Indicates the specific function or part an entity has within the context of the Guitar Hero game (e.g., player role, character role, or gameplay position).
-
E.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b9be988190b5e3804c39dc7dd9 |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.