Triple
T31528209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schubert piano sonatas |
E804401
|
entity |
| Predicate | publisherOfFirstEditions |
P7323
|
FINISHED |
| Object | Diabelli |
—
|
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: Diabelli | Statement: [Schubert piano sonatas, publisherOfFirstEditions, Diabelli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfFirstEditions Context triple: [Schubert piano sonatas, publisherOfFirstEditions, Diabelli]
-
A.
firstPublisher
chosen
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
B.
firstCompleteEditionPublisher
Indicates the publisher responsible for issuing the first complete edition of a work.
-
C.
publisherOfCollectedEdition
Indicates that an entity serves as the publisher responsible for issuing a collected edition of a work or set of works.
-
D.
authoritativeEditionPublisher
Indicates that an entity is the publisher responsible for issuing the authoritative or officially recognized edition of a work.
-
E.
publisherOfPrintVersion
Indicates that an entity serves as the publisher responsible for the printed (physical) version of another 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 30, 2026, 9:59 p.m.