Triple
T32981146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWV 63 |
E843800
|
entity |
| Predicate | WagnerWorkNumbering |
P92130
|
FINISHED |
| Object | WWV 63 |
—
|
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: WWV 63 | Statement: [WWV 63, WagnerWorkNumbering, WWV 63]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WagnerWorkNumbering Context triple: [WWV 63, WagnerWorkNumbering, WWV 63]
-
A.
WagnerCatalogueNumber
chosen
Indicates the specific catalogue number assigned to a work in the thematic catalogue of Richard Wagner’s compositions.
-
B.
WagnerCataloguePosition
Indicates the position or ordering of a work within a catalog or systematic listing of Wagner’s compositions.
-
C.
workNumberInBrahmsOeuvre
Indicates the catalog or opus number assigned to a specific work within Brahms’s complete body of compositions.
-
D.
workNumberInSchubertCatalogue
Indicates that one entity specifies the identifying work number assigned to a composition within the Schubert catalogue for another entity.
-
E.
workNumberWithinCantata
Indicates that a musical work’s number is specified within the ordered sequence of pieces that make up a cantata.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1dc8a108190a994bd39350129fe |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.