Triple
T29853671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Des Baches Wiegenlied |
E758128
|
entity |
| Predicate | endingFunctionInCycle |
P34990
|
FINISHED |
| Object | epilogue |
—
|
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: epilogue | Statement: [Des Baches Wiegenlied, endingFunctionInCycle, epilogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingFunctionInCycle Context triple: [Des Baches Wiegenlied, endingFunctionInCycle, epilogue]
-
A.
includedInCycle
Indicates that an entity participates in and is part of a closed loop or recurring sequence within a system or structure.
-
B.
endedFunctionallyWith
chosen
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
C.
cycleConsistsOf
Indicates that a cycle is composed of, or made up from, the specified component elements or segments.
-
D.
hasNumberInCycle
Indicates that a given number appears within a specified repeating sequence or cycle associated with an entity or process.
-
E.
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.
- 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_69f67649d26481909889228a8ca1af93 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:45 p.m.