Triple
T29026251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Träumerei |
E737600
|
entity |
| Predicate | isFrequentlyPerformedAsStandalonePiece |
P166909
|
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, isFrequentlyPerformedAsStandalonePiece, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyPerformedAsStandalonePiece Context triple: [Träumerei, isFrequentlyPerformedAsStandalonePiece, true]
-
A.
isSoloPerformance
Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
-
B.
frequentSoloInstrument
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
-
C.
isOftenPerformedWithExtendedSolo
Indicates that an action or performance is frequently carried out including a prolonged or elaborated solo section.
-
D.
isFrequentlyPerformedBy
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
E.
performedIndividually
Indicates that the action or activity was carried out by a single individual rather than collaboratively or as part of a group.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 9:52 a.m.