Triple
T29026266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Träumerei |
E737600
|
entity |
| Predicate | includedInStandardPianoRepertoire |
P105958
|
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: [Träumerei, includedInStandardPianoRepertoire, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInStandardPianoRepertoire Context triple: [Träumerei, includedInStandardPianoRepertoire, true]
-
A.
includedInStandardRepertoire
chosen
Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
-
B.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
-
C.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
D.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
-
E.
hasPianoStyle
Indicates that one entity possesses, is associated with, or is characterized by a particular style or manner of piano playing.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: April 28, 2026, 9:52 a.m.