Triple
T24511391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto "Concentric Paths" |
E606228
|
entity |
| Predicate | soloPartCharacteristic |
P156562
|
FINISHED |
| Object | virtuosic |
—
|
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 | Statement: [Violin Concerto "Concentric Paths", soloPartCharacteristic, virtuosic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soloPartCharacteristic Context triple: [Violin Concerto "Concentric Paths", soloPartCharacteristic, virtuosic]
-
A.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
-
B.
sonCharacteristic
Indicates that a son possesses or exhibits a particular characteristic or attribute in relation to something or someone.
-
C.
frequentSoloInstrument
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
-
D.
soloistRole
Indicates that an entity has the role of performing as a soloist within a work, event, or performance.
-
E.
sharedCharacteristic
Indicates that two or more entities possess the same specified attribute or quality.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:24 a.m.