Triple
T8813625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich von Ofterdingen |
E209724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romantic literature work |
C4035
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Romantic literature work Context triple: [Heinrich von Ofterdingen, instanceOf, Romantic literature work]
-
A.
Romantic poem
A romantic poem is a lyrical composition that expresses deep emotions, idealized love, and personal reflection, often using rich imagery and musical language to evoke passion and longing.
-
B.
romanticism
Romanticism is a cultural and artistic movement that emphasizes emotion, individual experience, imagination, and a deep appreciation of nature, often in reaction against rationalism and industrialization.
-
C.
literaryWork
chosen
A literaryWork is a created written or spoken artistic composition, such as a novel, poem, or play, that conveys ideas, stories, or emotions through language.
-
D.
English Renaissance literature work
An English Renaissance literature work is a text—such as a poem, play, or prose narrative—produced in England roughly between the late 15th and early 17th centuries, characterized by humanist themes, experimentation with form, and a revitalized interest in classical antiquity.
-
E.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
- F. None of above.
Provenance (1 batch)
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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.