Triple
T32163349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mal Waldron |
E821487
|
entity |
| Predicate | wasPianistFor |
P60329
|
FINISHED |
| Object | Billie Holiday |
—
|
NE NERFINISHED |
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: Billie Holiday | Statement: [Mal Waldron, wasPianistFor, Billie Holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPianistFor Context triple: [Mal Waldron, wasPianistFor, Billie Holiday]
-
A.
hasPianist
Indicates that an entity is associated with or features a pianist, typically specifying who performs the piano part in a work, event, or group.
-
B.
firstPerformerPiano
Indicates that the referenced entity is the first (primary or earliest) performer on the piano in a given performance or musical context.
-
C.
workedAsSessionMusicianFor
chosen
Indicates that one entity performed as a session musician providing musical services or recordings for another entity, typically an artist, band, or production.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
hasViolinist
Indicates that an entity is associated with or includes a violinist as part of its composition, membership, or participants.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1de3548190b51d38e380bc67ef |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:33 a.m.