Triple
T31490426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridal Chorus |
E803389
|
entity |
| Predicate | publisherOfEarlyEditions |
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: [Bridal Chorus, publisherOfEarlyEditions, Breitkopf & Härtel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfEarlyEditions Context triple: [Bridal Chorus, publisherOfEarlyEditions, Breitkopf & Härtel]
-
A.
publisherOfEarlyComics
Indicates that an entity served as the publisher responsible for releasing early comic works of another entity.
-
B.
publisherOfCriticalEdition
Indicates that an entity serves as the publisher responsible for issuing a critical (scholarly edited and annotated) 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.
firstPublisher
chosen
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
E.
firstUKPublisher
Indicates that the subject was the first entity to publish the object in the United Kingdom.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 30, 2026, 9:38 p.m.