Triple
T33967265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite No. 3 in G major, Op. 55 |
E870887
|
entity |
| Predicate | hasKeyOfFirstMovement |
P40256
|
FINISHED |
| Object | G 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: G major | Statement: [Suite No. 3 in G major, Op. 55, hasKeyOfFirstMovement, G major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOfFirstMovement Context triple: [Suite No. 3 in G major, Op. 55, hasKeyOfFirstMovement, G major]
-
A.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
-
B.
firstMovementKey
chosen
Indicates the musical key in which the first movement of a multi-movement work is composed.
-
C.
hasOpeningMovement
Indicates that a work, performance, or sequence includes a distinct initial movement or section that begins the overall piece.
-
D.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
E.
hasMovementOrder
Indicates that one entity is assigned or associated with a specific directive or sequence for movement or relocation.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 1, 2026, 1:50 a.m.