Triple
T31362081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Brubeck Pieces |
E799903
|
entity |
| Predicate | usesMusicComposedBy |
P47024
|
FINISHED |
| Object | Dave Brubeck |
—
|
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: Dave Brubeck | Statement: [Four Brubeck Pieces, usesMusicComposedBy, Dave Brubeck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMusicComposedBy Context triple: [Four Brubeck Pieces, usesMusicComposedBy, Dave Brubeck]
-
A.
composedForMusicBy
Indicates that a musical work was specifically created or written by a particular composer.
-
B.
hasMusicalComposer
chosen
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
C.
musicOrchestratedBy
Indicates that a piece of music or musical work is arranged or orchestrated by a specific person or entity.
-
D.
producedComposer
Indicates that one entity served as the producer for a musical work created or composed by another entity.
-
E.
usesMusicFor
Indicates that one entity employs or applies music as a means, tool, or resource to achieve or support some purpose, activity, or effect for another entity or context.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 9:18 p.m.