Triple
T23707818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bouncing with Bud |
E585774
|
entity |
| Predicate | keyPerformerRole |
P24740
|
FINISHED |
| Object | pianist |
—
|
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: pianist | Statement: [Bouncing with Bud, keyPerformerRole, pianist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPerformerRole Context triple: [Bouncing with Bud, keyPerformerRole, pianist]
-
A.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
B.
performingArtRole
Indicates a role or function that an entity fulfills within the context of a performing arts activity or production.
-
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.
peakRole
Indicates the role or position an entity holds at the highest or most prominent point of its activity, status, or performance.
-
E.
keyInManyPerformances
Indicates that the entity serves as a central or essential element in numerous performances or events.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b68868ac8190824cdd7eb9fb2f06 |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.