Triple
T31358814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Andante elegiaco |
E799807
|
entity |
| Predicate | parentWorkKey |
P101522
|
FINISHED |
| Object | D 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: D major | Statement: [III. Andante elegiaco, parentWorkKey, D major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentWorkKey Context triple: [III. Andante elegiaco, parentWorkKey, D major]
-
A.
parentWorkPublisher
Indicates that a publisher is responsible for publishing the parent (containing or overarching) work of the given entity.
-
B.
parentWorksAt
Indicates that the parent of a given person is employed at a specified organization or workplace.
-
C.
parentWorkTitle
Indicates that the value is the title of a larger or original work of which the current item is a part, adaptation, or derivative.
-
D.
associatedWorkKey
chosen
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.
-
E.
parentWorkSignificance
Indicates the degree of importance or influence that a parent work has on the related work or 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 9:17 p.m.