Triple
T27716752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Johnny Dankworth Orchestra |
E698838
|
entity |
| Predicate | hasBandLeaderRole |
P118484
|
FINISHED |
| Object | saxophonist |
—
|
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: saxophonist | Statement: [The Johnny Dankworth Orchestra, hasBandLeaderRole, saxophonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandLeaderRole Context triple: [The Johnny Dankworth Orchestra, hasBandLeaderRole, saxophonist]
-
A.
bandLeader
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
B.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
C.
hasRoleInBand
chosen
Indicates that an entity holds a specific role or position within a band.
-
D.
musicalEnsembleRole
Indicates the specific function or position an individual holds within a musical ensemble, such as performer, conductor, or composer.
-
E.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 3:05 p.m.