Triple
T32805550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forellenquintett |
E839010
|
entity |
| Predicate | associatedSongTitle |
P2152
|
FINISHED |
| Object | Die Forelle |
E839007
|
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: Die Forelle | Statement: [Forellenquintett, associatedSongTitle, Die Forelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSongTitle Context triple: [Forellenquintett, associatedSongTitle, Die Forelle]
-
A.
titleSongFor
Indicates that a song serves as the title track for a particular work, such as an album, film, or show.
-
B.
hasSongTitle
Indicates that an entity (such as a song or musical work) bears or is associated with a specific song title.
-
C.
clubSongTitle
Indicates that a song serves as the official or associated song of a particular club, identified by its title.
-
D.
secondSongTitle
Indicates that the object is the title of the second song associated with the subject.
-
E.
associatedMusic
chosen
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34b178503081908a6880a045aa933f |
completed | June 19, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:15 a.m.