Triple
T23666088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adagio finale |
E584580
|
entity |
| Predicate | workNumberInMahlerOeuvre |
P86756
|
FINISHED |
| Object | Symphony No. 3 |
—
|
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: Symphony No. 3 | Statement: [Adagio finale, workNumberInMahlerOeuvre, Symphony No. 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInMahlerOeuvre Context triple: [Adagio finale, workNumberInMahlerOeuvre, Symphony No. 3]
-
A.
workNumberInMahlerSymphonies
chosen
Indicates the specific numbered position a work occupies within the sequence of Mahler’s symphonies.
-
B.
workNumberInBrahmsOeuvre
Indicates the catalog or opus number assigned to a specific work within Brahms’s complete body of compositions.
-
C.
workNumberInComposerChamberMusic
Indicates that a specific work number is assigned to a composer's piece within their body of chamber music.
-
D.
workNumberInBrucknerSymphonies
Indicates the specific ordinal number assigned to a work within the sequence of Bruckner’s symphonies.
-
E.
workNumberInBWV
Indicates that a musical work is identified by a specific catalog number within the Bach-Werke-Verzeichnis (BWV) catalog.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40b8bd48190922c7252e71a5421 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.