Triple
T8813912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impromptus, D. 899 |
E209730
|
entity |
| Predicate | opusNumberAssignedByPublisher |
P10579
|
FINISHED |
| Object | Op. 90 |
—
|
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: Op. 90 | Statement: [Impromptus, D. 899, opusNumberAssignedByPublisher, Op. 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusNumberAssignedByPublisher Context triple: [Impromptus, D. 899, opusNumberAssignedByPublisher, Op. 90]
-
A.
opusNumber
chosen
Indicates that a creative work is assigned a specific opus number identifying its place within a creator’s catalog or chronological sequence of works.
-
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.
correctedProofPublicationYear
Indicates the year in which a corrected version of a previously published proof was formally published.
-
D.
ownedPublication
Indicates that one entity possesses ownership or controlling rights over a particular publication.
-
E.
numberInAnthology
Indicates the specific position or sequence number that a work occupies within an anthology.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.