Triple
T30072518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler 6 |
E764223
|
entity |
| Predicate | nickNameUsage |
P163927
|
FINISHED |
| Object | often called the Tragic 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: often called the Tragic Symphony | Statement: [Mahler 6, nickNameUsage, often called the Tragic Symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nickNameUsage Context triple: [Mahler 6, nickNameUsage, often called the Tragic Symphony]
-
A.
usesNicknameIn
chosen
Indicates that one entity refers to another entity by a specific nickname within a particular context or setting.
-
B.
nicknameUsageTone
Indicates the tone or emotional quality conveyed when a particular nickname is used for someone or something.
-
C.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
D.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
E.
lineNickname
Indicates that one entity is an alternative or informal name (nickname) used to refer to a particular line (such as a route, service, or connection).
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d3a1a048190a40fef6e237dcf90 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:01 p.m.