Triple
T23294332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler Symphony No. 7 |
E590120
|
entity |
| Predicate | positionInMahlerOutput |
P41125
|
FINISHED |
| Object | fifth completed symphony |
—
|
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: fifth completed symphony | Statement: [Mahler Symphony No. 7, positionInMahlerOutput, fifth completed symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMahlerOutput Context triple: [Mahler Symphony No. 7, positionInMahlerOutput, fifth completed symphony]
-
A.
positionInOpus
Indicates the specific location or ordering of a part or element within a larger work or opus.
-
B.
positionInComposerOutput
chosen
Indicates that one entity occupies a specific position or index within the ordered output produced by a composer.
-
C.
placeInBrahmsOutput
Indicates that one entity occupies a specific position or location within the output or work produced by Brahms.
-
D.
positionInMass
Indicates that an entity occupies a specific location or role within a larger undifferentiated group, collection, or mass.
-
E.
positionInBand
Indicates the specific role or place an individual holds within a musical band.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cdce7081908ca1cf9107b87f61 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:02 p.m.