Triple
T19322562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristan chord |
E483262
|
entity |
| Predicate | commonSpellingRelativeToA |
P56633
|
FINISHED |
| Object | F–B–D♯–G♯ |
—
|
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: F–B–D♯–G♯ | Statement: [Tristan chord, commonSpellingRelativeToA, F–B–D♯–G♯]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSpellingRelativeToA Context triple: [Tristan chord, commonSpellingRelativeToA, F–B–D♯–G♯]
-
A.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
-
B.
hasTypicalSpelling
chosen
Indicates that one form is the standard or commonly accepted spelling of another form.
-
C.
canBeCorrectedTo
Indicates that one entity can be modified or adjusted so that it becomes equivalent to or matches another entity.
-
D.
spellingStyle
Indicates the particular orthographic convention or system of spelling that is used or preferred in a given context.
-
E.
originalSpelling
Indicates that one entity provides the initial or historically first-used spelling form of another entity’s name or term.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8948948190b76a384041333509 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.