Triple
T13748135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenny G Live |
E330269
|
entity |
| Predicate | hasPerformerAttribute |
P41712
|
FINISHED |
| Object | virtuosic saxophone playing |
—
|
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: virtuosic saxophone playing | Statement: [Kenny G Live, hasPerformerAttribute, virtuosic saxophone playing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerAttribute Context triple: [Kenny G Live, hasPerformerAttribute, virtuosic saxophone playing]
-
A.
hasPerformerCharacteristic
chosen
Indicates that a performer possesses a particular attribute, quality, or characteristic.
-
B.
hasPerformerGivenName
Indicates that a performer is associated with a specific given (first) name.
-
C.
hasPerformerBackground
Indicates that an entity has a specific background, experience, or history as a performer.
-
D.
hasKeyPerformerOnRecording
Indicates that a particular performer is a principal or featured contributor on a specific recording.
-
E.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02132a108190aca728b95e83af01 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.