Triple
T30017330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler's Fifth Symphony |
E762630
|
entity |
| Predicate | alternativeKey |
P139918
|
FINISHED |
| Object | D major |
—
|
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: D major | Statement: [Mahler's Fifth Symphony, alternativeKey, D major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeKey Context triple: [Mahler's Fifth Symphony, alternativeKey, D major]
-
A.
associatedKey
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another entity.
-
B.
keyAttribute
Indicates that the specified attribute is a primary or defining characteristic that uniquely identifies or is essential to the entity within a given context.
-
C.
hasAlternateKey
chosen
Indicates that an entity is associated with an additional, non-primary identifier that can uniquely distinguish it as an alternative to the primary key.
-
D.
alternativeIdentification
Indicates that one entity serves as an alternative identifier or reference for another entity.
-
E.
alternativeFlag
Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 6:46 p.m.