Triple
T8469807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Schumann: Novelletten, Op. 21 |
E200251
|
entity |
| Predicate | keyOfPiece4 |
P40267
|
FINISHED |
| Object | D major |
—
|
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: D major | Statement: [Robert Schumann: Novelletten, Op. 21, keyOfPiece4, D major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfPiece4 Context triple: [Robert Schumann: Novelletten, Op. 21, keyOfPiece4, D major]
-
A.
keyOfPart
Indicates that one entity functions as the key or identifier used to reference, access, or distinguish a specific part of another entity.
-
B.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
-
C.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
-
D.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
E.
fourthMovementKey
chosen
Indicates the musical key in which the fourth movement of a multi-movement work is composed or performed.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d5dd088190a79050417f527f14 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.