Triple
T29853441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgengruß |
E758122
|
entity |
| Predicate | cycleNumberInSchubertCatalog |
P173739
|
FINISHED |
| Object | D 795 |
—
|
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: D 795 | Statement: [Morgengruß, cycleNumberInSchubertCatalog, D 795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleNumberInSchubertCatalog Context triple: [Morgengruß, cycleNumberInSchubertCatalog, D 795]
-
A.
workNumberInSchubertCatalogue
Indicates that one entity specifies the identifying work number assigned to a composition within the Schubert catalogue for another entity.
-
B.
cycleNumberInDichterliebe
Indicates the specific position or sequence number that a given item occupies within the song cycle "Dichterliebe."
-
C.
cycleNumberInDieSchöneMüllerin
Indicates the specific position or sequence number of a song within the song cycle "Die schöne Müllerin."
-
D.
inBeethovenPianoSonataCycle
Indicates that something is part of, or occurs within, the cycle of Beethoven’s piano sonatas.
-
E.
catalogueNumberOfCycle
Indicates that an entity is assigned a specific catalogue number identifying a particular cycle within a cataloging system.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 29, 2026, 5:45 p.m.