Triple
T29027053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die alten, bösen Lieder |
E737620
|
entity |
| Predicate | catalogueNumberOfCycle |
P165938
|
FINISHED |
| Object | Dichterliebe Op. 48 |
—
|
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: Dichterliebe Op. 48 | Statement: [Die alten, bösen Lieder, catalogueNumberOfCycle, Dichterliebe Op. 48]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueNumberOfCycle Context triple: [Die alten, bösen Lieder, catalogueNumberOfCycle, Dichterliebe Op. 48]
-
A.
typicalNumberOfCycles
Indicates the usual or characteristic count of cycles associated with an entity, process, or event.
-
B.
opusNumberOfCycle
Indicates that a specific opus number identifies or is assigned to a particular musical cycle.
-
C.
numberOfStrokesPerCycle
Indicates the count of individual strokes that occur during one complete cycle of a repeated action or process.
-
D.
hasNumberInCycle
Indicates that a given number appears within a specified repeating sequence or cycle associated with an entity or process.
-
E.
hasQuantityPerCycle
Indicates a relationship where a specific quantity is associated with each occurrence or cycle of a repeated process or event.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6600b2ea0819080d54e0400bd3364 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:53 a.m.