Triple
T20876271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For No One |
E514024
|
entity |
| Predicate | featuresInstrumentSolo |
P69077
|
FINISHED |
| Object | French horn solo |
—
|
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: French horn solo | Statement: [For No One, featuresInstrumentSolo, French horn solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresInstrumentSolo Context triple: [For No One, featuresInstrumentSolo, French horn solo]
-
A.
instrumentalSoloist
chosen
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
B.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
-
C.
featuresInstrumentSection
Indicates that an entity includes or highlights a specific section devoted to musical instruments.
-
D.
featuresPrimaryInstrument
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).
-
E.
arrangedSoloInstrument
Indicates that a musical work has been arranged specifically for performance by a single solo instrument.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c674f68c8190a7b43aeea5b9b976 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.