Triple
T31613140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 4 in D minor, Op. 70 |
E806679
|
entity |
| Predicate | hasVirtuosityLevel |
P83475
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Piano Concerto No. 4 in D minor, Op. 70, hasVirtuosityLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirtuosityLevel Context triple: [Piano Concerto No. 4 in D minor, Op. 70, hasVirtuosityLevel, high]
-
A.
virtuosityLevel
chosen
Indicates the degree or extent of exceptional skill or mastery demonstrated in performing an action or activity.
-
B.
hasArtisticLevel
Indicates the degree or quality of artistic skill, sophistication, or creativity associated with an entity.
-
C.
expressiveVirtuosity
Indicates a relationship where an entity demonstrates exceptional technical skill combined with deep emotional or artistic expressiveness in its performance or creation.
-
D.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
E.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 30, 2026, 10:37 p.m.