Triple
T25035369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Barnet Orchestra |
E626964
|
entity |
| Predicate | notableInstrumentOfLeader |
P9123
|
FINISHED |
| Object | saxophone |
—
|
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: saxophone | Statement: [Charlie Barnet Orchestra, notableInstrumentOfLeader, saxophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInstrumentOfLeader Context triple: [Charlie Barnet Orchestra, notableInstrumentOfLeader, saxophone]
-
A.
mainInstrumentOfLeader
Indicates that an instrument is the primary or most characteristic instrument used by a particular leader (such as a bandleader or ensemble leader).
-
B.
notableInstrument
chosen
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
C.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
D.
typicalLeadInstrument
Indicates that an instrument is commonly used as the primary or lead instrument in a given musical context or performance.
-
E.
bandLeader
Indicates that one entity serves as the leader or primary directing figure of a musical band that includes the other entity.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 18, 2026, 6:08 a.m.