Triple
T33967264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite No. 3 in G major, Op. 55 |
E870887
|
entity |
| Predicate | hasKeyOfFinale |
P146147
|
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, hasKeyOfFinale, G major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyOfFinale Context triple: [Suite No. 3 in G major, Op. 55, hasKeyOfFinale, G major]
-
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.
keyOfFinale
chosen
Indicates the musical key in which the final or last movement/section of a work is set.
-
C.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
D.
hasFinaleWithChoraleElements
Indicates that the finale of a work includes or is characterized by chorale-style musical elements.
-
E.
hasLiveFinale
Indicates that an event, show, or series concludes with a final installment that is broadcast or performed live.
- 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_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:50 a.m.