Triple
T32805261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Doppelgänger |
E839003
|
entity |
| Predicate | composerOfCycle |
P192790
|
FINISHED |
| Object | Franz Schubert |
—
|
NE NERFINISHED |
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: Franz Schubert | Statement: [Der Doppelgänger, composerOfCycle, Franz Schubert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOfCycle Context triple: [Der Doppelgänger, composerOfCycle, Franz Schubert]
-
A.
cycleAuthor
Indicates that an entity is the author or creator responsible for a particular cycle (such as a recurring process, sequence, or version cycle).
-
B.
composerOfTextCycle
Indicates that one entity is the creator or writer of the textual content for a multi-part or cyclical work associated with another entity.
-
C.
combinesCycle
Indicates that one entity merges or integrates its cycle with that of another entity to form a combined or unified cycle.
-
D.
composerOfCataloguedWork
Indicates that one entity is the composer or creator of a specific catalogued musical or artistic work associated with another entity.
-
E.
composerOfMainWork
Indicates that one entity is the composer who created the primary or main work associated with 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
| PDg | Predicate description generation | batch_69fd2a2095f88190bfcbcb2973516ffc |
completed | May 8, 2026, 12:11 a.m. |
Created at: May 1, 2026, 1:15 a.m.