Triple
T33967262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite No. 3 in G major, Op. 55 |
E870887
|
entity |
| Predicate | hasFinaleType |
P83468
|
FINISHED |
| Object | theme and variations |
—
|
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: theme and variations | Statement: [Suite No. 3 in G major, Op. 55, hasFinaleType, theme and variations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinaleType Context triple: [Suite No. 3 in G major, Op. 55, hasFinaleType, theme and variations]
-
A.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
B.
hasFinaleMovement
chosen
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
C.
hasLiveFinale
Indicates that an event, show, or series concludes with a final installment that is broadcast or performed live.
-
D.
hasFinaleWithChoraleElements
Indicates that the finale of a work includes or is characterized by chorale-style musical elements.
-
E.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
- 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_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:50 a.m.