Triple
T29027048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die alten, bösen Lieder |
E737620
|
entity |
| Predicate | cycleConcludingSong |
P55758
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Die alten, bösen Lieder, cycleConcludingSong, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleConcludingSong Context triple: [Die alten, bösen Lieder, cycleConcludingSong, true]
-
A.
finalSong
chosen
Indicates that a song is the last or concluding piece within a sequence, collection, or performance.
-
B.
cycleBy
Indicates that one entity moves or travels by means of riding a bicycle (or similar cycle) in relation to another entity or context.
-
C.
cycleWith
Indicates that two or more entities participate together in a cycling activity, such as riding bicycles along the same route or at the same time.
-
D.
hasSongCycle
Indicates that one entity (typically a musical work or collection) includes or is associated with a specific song cycle as part of its structure or content.
-
E.
cyclePosition
Indicates the relative location or order of something within a repeating or cyclical sequence.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 9:53 a.m.