Triple
T33761832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Best of Jazz (BBC radio series) |
E865125
|
entity |
| Predicate | hasBandleaderPresenter |
P56624
|
FINISHED |
| Object | Humphrey Lyttelton |
—
|
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: Humphrey Lyttelton | Statement: [The Best of Jazz (BBC radio series), hasBandleaderPresenter, Humphrey Lyttelton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandleaderPresenter Context triple: [The Best of Jazz (BBC radio series), hasBandleaderPresenter, Humphrey Lyttelton]
-
A.
hasBandLeaderRoleOf
Indicates that one entity serves in the role of band leader for another entity (typically a band or musical group).
-
B.
bandLeader
chosen
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
-
C.
houseBandLeader
Indicates that one entity serves as the leader of a house band associated with another entity (such as a venue, show, or organization).
-
D.
hasImpresario
Indicates that an entity is associated with, or managed/promoted by, an impresario.
-
E.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 1, 2026, 1:45 a.m.