Triple
T23227920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barcarolles for piano |
E581062
|
entity |
| Predicate | opusNumberRange |
P151443
|
FINISHED |
| Object | Op. 26–Op. 116 |
—
|
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. 26–Op. 116 | Statement: [Barcarolles for piano, opusNumberRange, Op. 26–Op. 116]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusNumberRange Context triple: [Barcarolles for piano, opusNumberRange, Op. 26–Op. 116]
-
A.
opusNumber
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.
articleNumberRange
Indicates that something is associated with or falls within a specified range of article numbers.
-
C.
publicationNumber
Indicates the unique identifying number assigned to a specific publication within a cataloging or publishing system.
-
D.
serialNumberRange
Indicates that there is a specified range of serial numbers within which the related entities or items fall.
-
E.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192302e508190b286c284a261f172 |
completed | April 29, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:09 p.m.