Triple
T37922251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biamonti 247 |
E945994
|
entity |
| Predicate | relatedWorkNickname |
P101523
|
FINISHED |
| Object | Moonlight Sonata |
E947792
|
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: Moonlight Sonata | Statement: [Biamonti 247, relatedWorkNickname, Moonlight Sonata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkNickname Context triple: [Biamonti 247, relatedWorkNickname, Moonlight Sonata]
-
A.
associatedNicknameOfWork
chosen
Indicates that a given nickname or informal title is commonly used to refer to a particular work.
-
B.
dedicatedToOrNicknameOf
Indicates that one entity is either the dedicatee of something (e.g., a work, object, or honor) or serves as an alternative name or nickname for another entity.
-
C.
propNickname
Indicates that one entity is used as a nickname or informal alternative name for another entity.
-
D.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
E.
associatedWithArtistNickname
Indicates that an entity is connected to or identified by a particular artist’s nickname or pseudonym.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117ef25b081908bf4f98c83dafcd8 |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.