Triple
T19426493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bells, Op. 35 |
E485991
|
entity |
| Predicate | opusNumberOfComposer |
P135845
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [The Bells, Op. 35, opusNumberOfComposer, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusNumberOfComposer Context triple: [The Bells, Op. 35, opusNumberOfComposer, 35]
-
A.
workNumberInComposerChamberMusic
Indicates that a specific work number is assigned to a composer's piece within their body of chamber music.
-
B.
producedComposer
Indicates that one entity served as the producer for a musical work created or composed by another entity.
-
C.
operaNumberInComposerOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of works by a specific composer.
-
D.
publishedComposer
Indicates that a composer has had their musical works formally published, typically by a recognized publisher or label.
-
E.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63219f27481909fe686209defc971 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.