Triple
T31869141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Jacquet Big Band |
E813547
|
entity |
| Predicate | hasPrimarySoloist |
P118260
|
FINISHED |
| Object | Illinois Jacquet |
—
|
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: Illinois Jacquet | Statement: [Illinois Jacquet Big Band, hasPrimarySoloist, Illinois Jacquet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySoloist Context triple: [Illinois Jacquet Big Band, hasPrimarySoloist, Illinois Jacquet]
-
A.
hasPrimaryMusician
chosen
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
C.
hasBassSolo
Indicates that a musical piece, section, or performance includes a solo passage specifically played by the bass instrument.
-
D.
isSoloPerformance
Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
-
E.
isSoloDebutOf
Indicates that an event, work, or performance is the first solo appearance or release of a particular individual.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: April 30, 2026, 11:54 p.m.