Triple
T29180348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonate Nr. 2 g-Moll, Op. 22 |
E739728
|
entity |
| Predicate | virtuosic |
P83476
|
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: [Sonate Nr. 2 g-Moll, Op. 22, virtuosic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: virtuosic Context triple: [Sonate Nr. 2 g-Moll, Op. 22, virtuosic, true]
-
A.
virtuosicDemands
chosen
Indicates that an action, performance, or task requires exceptional technical skill, mastery, or virtuosity from the entity performing it.
-
B.
virtuosityLevel
Indicates the degree or extent of exceptional skill or mastery demonstrated in performing an action or activity.
-
C.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
D.
virtuosicWritingFor
Indicates that one entity exhibits exceptionally skilled or masterful writing specifically created for another entity.
-
E.
visionary
Indicates that an entity is recognized for having original, forward-thinking ideas or plans that anticipate future developments.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663444268819088b7976a7295d57a |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:57 a.m.