Triple
T30705106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act I of The Nutcracker |
E781729
|
entity |
| Predicate | musicKeyIncludes |
P12877
|
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: [Act I of The Nutcracker, musicKeyIncludes, G major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicKeyIncludes Context triple: [Act I of The Nutcracker, musicKeyIncludes, G major]
-
A.
musicKey
chosen
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
B.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
C.
musicMotif
Indicates a recurring musical idea, theme, or pattern that appears multiple times within a composition or across related works.
-
D.
musicField
Indicates a relationship where an entity is associated with a particular field, genre, or domain within music.
-
E.
musicUsed
Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 29, 2026, 8:35 p.m.