Triple
T8281826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellingtons Sieg oder die Schlacht bei Vittoria |
E193690
|
entity |
| Predicate | workNumberInBeethovenOeuvre |
P32662
|
FINISHED |
| Object | Opus 91 |
—
|
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: Opus 91 | Statement: [Wellingtons Sieg oder die Schlacht bei Vittoria, workNumberInBeethovenOeuvre, Opus 91]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInBeethovenOeuvre Context triple: [Wellingtons Sieg oder die Schlacht bei Vittoria, workNumberInBeethovenOeuvre, Opus 91]
-
A.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
B.
inBeethovenPianoSonataCycle
Indicates that something is part of, or occurs within, the cycle of Beethoven’s piano sonatas.
-
C.
workNumberInComposerOutput
chosen
Indicates that a specific work number appears in the output or catalog produced by a particular composer.
-
D.
eraWithinBeethovenOutput
Indicates that a given time period falls within the historical era corresponding to Beethoven’s active creative output.
-
E.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ef8508819098112a3397c96ca5 |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70ad9fc081908741f8c4a4141edf |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.