Triple
T32742288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Das Trinklied vom Jammer der Erde |
E837247
|
entity |
| Predicate | cycleOrderPrecedes |
P172169
|
FINISHED |
| Object | Der Einsame im Herbst |
—
|
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: Der Einsame im Herbst | Statement: [Das Trinklied vom Jammer der Erde, cycleOrderPrecedes, Der Einsame im Herbst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleOrderPrecedes Context triple: [Das Trinklied vom Jammer der Erde, cycleOrderPrecedes, Der Einsame im Herbst]
-
A.
cyclePrecededBy
chosen
Indicates that one cycle occurs earlier in sequence or time than another specified cycle.
-
B.
hasCycleOrder
Indicates that there is a defined cyclic sequence or ordering among a set of related elements or events.
-
C.
cycleConsistsOf
Indicates that a cycle is composed of, or made up from, the specified component elements or segments.
-
D.
cycleFollowedBy
Indicates that one cycle occurs immediately after or as a direct successor to another cycle in a sequence or process.
-
E.
successorInCycle
Indicates that one entity directly follows another as the next element in a repeating cyclic order.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:12 a.m.