Triple
T32805328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rellstab songs |
E839005
|
entity |
| Predicate | keyWorkIn |
P175136
|
FINISHED |
| Object | Schubert’s late song output |
—
|
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: Schubert’s late song output | Statement: [Rellstab songs, keyWorkIn, Schubert’s late song output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyWorkIn Context triple: [Rellstab songs, keyWorkIn, Schubert’s late song output]
-
A.
keyOfWork
Indicates that one entity specifies the musical key in which a particular work is composed or performed.
-
B.
keyWorkOf
Indicates that the subject is a central, defining, or most important work created by the object (such as an artist, author, or creator).
-
C.
keyOfLastWork
Indicates the musical key in which an entity’s most recently created or performed work is set.
-
D.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
E.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
- F. None of above. chosen
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_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:15 a.m.