Triple
T30906132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonie in h-Moll |
E787304
|
entity |
| Predicate | associatedNicknameForm |
P56482
|
FINISHED |
| Object | Unfinished Symphony |
E785518
|
NE 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: Unfinished Symphony | Statement: [Sinfonie in h-Moll, associatedNicknameForm, Unfinished Symphony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedNicknameForm Context triple: [Sinfonie in h-Moll, associatedNicknameForm, Unfinished Symphony]
-
A.
hasNicknameForm
chosen
Indicates that one entity is a nickname or informal variant form of another entity’s name.
-
B.
pairedNickname
Indicates that two entities share or are associated with a complementary or matching set of nicknames.
-
C.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
D.
propNickname
Indicates that one entity is used as a nickname or informal alternative name for another entity.
-
E.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
- F. None of above.
Provenance (4 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fba07ed8819096aa282c77c559b8 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:50 p.m.