Triple
T29026150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Dichter spricht |
E737597
|
entity |
| Predicate | associatedCycleTitle |
P5175
|
FINISHED |
| Object | Kinderszenen |
E200227
|
NE 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: Kinderszenen | Statement: [Der Dichter spricht, associatedCycleTitle, Kinderszenen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCycleTitle Context triple: [Der Dichter spricht, associatedCycleTitle, Kinderszenen]
-
A.
associatedEpicCycle
Indicates that one entity is linked to, or forms part of, a particular epic cycle within a larger narrative or project structure.
-
B.
associatedKeyOfCycle
Indicates a relationship where a key is linked to or derived from a specific cycle within a process, structure, or system.
-
C.
associatedTitle
chosen
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
D.
associatedWithAuthorCycle
Indicates a relationship where an entity is linked to a recurring or cyclical pattern involving an author, such as repeated collaborations, works, or roles over time.
-
E.
cycleTitleTranslation
Indicates that one title is a translated version of another title for the same cycle or series.
- F. None of above.
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_6a02f847b9848190a9fedbc411ae0918 |
completed | May 12, 2026, 9:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25d8f87ec4819085a702870a5ec2cf |
completed | June 7, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_6a02f556860c8190b2995433fa05fdd0 |
completed | May 12, 2026, 9:39 a.m. |
Created at: April 28, 2026, 9:52 a.m.