Triple
T29028890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild und lustig (No. 13) |
E737670
|
entity |
| Predicate | isCharacterPieceOf |
P165941
|
FINISHED |
| Object | Davidsbündlertänze, Op. 6 |
—
|
NE NERFINISHED |
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: Davidsbündlertänze, Op. 6 | Statement: [Wild und lustig (No. 13), isCharacterPieceOf, Davidsbündlertänze, Op. 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharacterPieceOf Context triple: [Wild und lustig (No. 13), isCharacterPieceOf, Davidsbündlertänze, Op. 6]
-
A.
usesPieceType
Indicates that one entity employs or operates using a specific type or category of piece as part of its function or activity.
-
B.
keyOfPiece2
Indicates that an entity serves as the musical key associated with a second piece or version of a composition.
-
C.
isMinorFigureIn
Indicates that an entity plays a small, secondary, or relatively insignificant role within another entity, such as a work, event, or context.
-
D.
keyOfPiece7
Indicates that something is the musical key associated with piece number 7.
-
E.
characterCorrespondsTo
Indicates that one character is equivalent to, maps onto, or represents another character in a defined correspondence or mapping.
- 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_69f6600bfbf081909eb61c47571e0277 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:54 a.m.