Triple
T28787156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Bryant |
E726845
|
entity |
| Predicate | workedAsSidemanWith |
P110830
|
FINISHED |
| Object | Miles Davis |
—
|
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: Miles Davis | Statement: [Ray Bryant, workedAsSidemanWith, Miles Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedAsSidemanWith Context triple: [Ray Bryant, workedAsSidemanWith, Miles Davis]
-
A.
workedAsSessionMusicianFor
Indicates that one entity performed as a session musician providing musical services or recordings for another entity, typically an artist, band, or production.
-
B.
musicalCollaborator
chosen
Indicates a relationship where two or more entities work together in creating, performing, or producing music.
-
C.
playedWithBandFrom
Indicates that an individual has performed as a member or guest with a musical band originating from a specified place or organization.
-
D.
partnerInQuartetWith
Indicates that two entities are members of the same quartet and are partners within that four-member group.
-
E.
partnerInMusicDuoWith
Indicates that two entities are members of the same musical duo, performing together as a two-person act.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:21 a.m.