Triple
T29853583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eifersucht und Stolz |
E758126
|
entity |
| Predicate | cycleTextAuthor |
P47504
|
FINISHED |
| Object | Wilhelm Müller |
—
|
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: Wilhelm Müller | Statement: [Eifersucht und Stolz, cycleTextAuthor, Wilhelm Müller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleTextAuthor Context triple: [Eifersucht und Stolz, cycleTextAuthor, Wilhelm Müller]
-
A.
cycleAuthor
chosen
Indicates that an entity is the author or creator responsible for a particular cycle (such as a recurring process, sequence, or version cycle).
-
B.
composerOfTextSetting
Indicates that one entity is the composer who created the musical setting for a text associated with another entity.
-
C.
theoreticalTextAuthor
Indicates that one entity is the author or creator of a theoretical or conceptual text associated with the other entity.
-
D.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
E.
authorMovement
Indicates that an author is associated with, influenced by, or identified as part of a particular artistic, literary, or intellectual movement.
- F. None of above.
Provenance (3 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 5:45 p.m.