Triple
T29528080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebestraum No. 3 |
E749120
|
entity |
| Predicate | publisherAtFirstPublication |
P7323
|
FINISHED |
| Object | Breitkopf & Härtel |
—
|
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: Breitkopf & Härtel | Statement: [Liebestraum No. 3, publisherAtFirstPublication, Breitkopf & Härtel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherAtFirstPublication Context triple: [Liebestraum No. 3, publisherAtFirstPublication, Breitkopf & Härtel]
-
A.
firstPublisher
chosen
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
B.
publisherOfWorkAppearingIn
Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
-
C.
publishedAuthor
Indicates that a person is the author of one or more works that have been formally published.
-
D.
placeOfFirstPublication
Indicates the location where a work was first published or made publicly available.
-
E.
authorPublished
Indicates that an author has published a particular work (such as a book, article, or paper).
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 4:49 p.m.