Triple
T16366034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Sanborn |
E397438
|
entity |
| Predicate | instrumentalRole |
P24740
|
FINISHED |
| Object | soloist |
—
|
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: soloist | Statement: [David Sanborn, instrumentalRole, soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentalRole Context triple: [David Sanborn, instrumentalRole, soloist]
-
A.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
B.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
C.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
D.
accompanimentRole
Indicates the role or function an accompanying entity plays in relation to a primary entity or event.
-
E.
musicSceneRole
Indicates the specific function or position an entity holds within a particular music scene or musical community.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3c915c81909e1757fc31921876 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.