Triple
T37922793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adagio un poco mosso |
E946008
|
entity |
| Predicate | parentWorkNumber |
P193315
|
FINISHED |
| Object | Piano Concerto No. 5 |
—
|
NE NERFINISHED |
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: Piano Concerto No. 5 | Statement: [Adagio un poco mosso, parentWorkNumber, Piano Concerto No. 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentWorkNumber Context triple: [Adagio un poco mosso, parentWorkNumber, Piano Concerto No. 5]
-
A.
parentWorkType
Indicates that one work is the broader or containing type/category from which another work type is derived or classified.
-
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.
linkedToWorkNumber
chosen
Indicates that one entity is associated with or references a specific work number as its identifier or linkage.
-
E.
parentWorkPublisher
Indicates that a publisher is responsible for publishing the parent (containing or overarching) work of the given entity.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:20 p.m.