Triple
T8813957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moments musicaux, D. 780 |
E209731
|
entity |
| Predicate | keyOf |
P84755
|
FINISHED |
| Object | C major (No. 1) |
—
|
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 (No. 1) | Statement: [Moments musicaux, D. 780, keyOf, C major (No. 1)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOf Context triple: [Moments musicaux, D. 780, keyOf, C major (No. 1)]
-
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.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
C.
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.
-
D.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
E.
keyIndex
Indicates the position or numerical index assigned to a specific key within an ordered set or collection of keys.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.