Triple
T34009242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockin' Chair (recording with Gene Krupa Orchestra) |
E872060
|
entity |
| Predicate | hasPrimarySoloInstrument |
P54631
|
FINISHED |
| Object | trumpet |
—
|
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: trumpet | Statement: [Rockin' Chair (recording with Gene Krupa Orchestra), hasPrimarySoloInstrument, trumpet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySoloInstrument Context triple: [Rockin' Chair (recording with Gene Krupa Orchestra), hasPrimarySoloInstrument, trumpet]
-
A.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
hasMajorInstrument
Indicates that an entity’s primary or main musical instrument is a specified instrument.
-
C.
featuresPrimaryInstrument
chosen
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
D.
frequentSoloInstrument
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
-
E.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a02206665508190ae2324d253ccf377 |
completed | May 11, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_6a021fdc6e54819082847bedd97a680b |
completed | May 11, 2026, 6:28 p.m. |
Created at: May 1, 2026, 1:51 a.m.