Triple
T13747971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duotones |
E330265
|
entity |
| Predicate | hasSaxophoneSolos |
P110819
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Duotones, hasSaxophoneSolos, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaxophoneSolos Context triple: [Duotones, hasSaxophoneSolos, true]
-
A.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
-
B.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
-
C.
hasGuitarSolo
Indicates that an entity (such as a song or performance) contains or features a guitar solo.
-
D.
featuresSaxophonist
Indicates that a musical work, performance, or recording prominently includes a saxophonist as part of its featured personnel.
-
E.
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.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:08 p.m.