Triple
T29026910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V. Lebhaft |
E737616
|
entity |
| Predicate | hasParentWorkKey |
P193247
|
FINISHED |
| Object | E-flat 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: E-flat major | Statement: [V. Lebhaft, hasParentWorkKey, E-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentWorkKey Context triple: [V. Lebhaft, hasParentWorkKey, E-flat major]
-
A.
hasParentWork
Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
-
B.
hasKeyOfWork
Indicates that one entity possesses or is associated with the key (tonal center) in which a work (such as a musical composition) is set.
-
C.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
D.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
-
E.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
| PDg | Predicate description generation | batch_69fd3d45ccb8819082f15e60bd33afc9 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 28, 2026, 9:53 a.m.