Triple
T5946371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Chopper |
E132290
|
entity |
| Predicate | frontmanRole |
P24740
|
FINISHED |
| Object | bassist |
—
|
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: bassist | Statement: [Bad Chopper, frontmanRole, bassist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontmanRole Context triple: [Bad Chopper, frontmanRole, bassist]
-
A.
primaryVocalist
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
-
B.
frontPerson
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
-
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.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
E.
frontlineRole
Indicates that an entity serves in a primary, direct-contact position at the forefront of an activity, operation, or service.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.