Triple
T10046345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Schumann: Nachtstücke, Op. 23 |
E207624
|
entity |
| Predicate | secondPieceKey |
P83481
|
FINISHED |
| Object | C 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: C major | Statement: [Robert Schumann: Nachtstücke, Op. 23, secondPieceKey, C major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondPieceKey Context triple: [Robert Schumann: Nachtstücke, Op. 23, secondPieceKey, C major]
-
A.
secondMovementKey
Indicates the musical key in which the second movement of a multi-movement work is composed.
-
B.
secondElement
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
-
C.
keyOfSeventhPiece
Indicates that something serves as the key (e.g., cryptographic or access key) specifically for the seventh piece in a sequence or collection.
-
D.
secondParty
Indicates that an entity participates in a relationship or transaction as the second party relative to a primary (first) party.
-
E.
keyOfPiece2
chosen
Indicates that an entity serves as the musical key associated with a second piece or version of a composition.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf648f548190a7aa3b1594665831 |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.