Triple
T36360021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doin' Allright |
E895462
|
entity |
| Predicate | instrumentationOfFreddieHubbard |
P12878
|
FINISHED |
| Object | trumpet |
—
|
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: trumpet | Statement: [Doin' Allright, instrumentationOfFreddieHubbard, trumpet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentationOfFreddieHubbard Context triple: [Doin' Allright, instrumentationOfFreddieHubbard, trumpet]
-
A.
vibraphonist
Indicates that one entity performs the role or action of playing the vibraphone in relation to another entity or context.
-
B.
instrumentsUsedBy
Indicates that a particular instrument, tool, or device is employed or utilized by a given entity to perform an action or achieve a result.
-
C.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
D.
featuresSaxophonist
Indicates that a musical work, performance, or recording prominently includes a saxophonist as part of its featured personnel.
-
E.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.