Triple
T6583585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernward Column |
E157362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottonian artwork |
C13464
|
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: Ottonian artwork Context triple: [Bernward Column, instanceOf, Ottonian artwork]
-
A.
medieval art
chosen
Medieval art is a broad category of visual works produced in Europe from roughly the 5th to the 15th century, characterized by religious themes, symbolic representation, and stylistic periods such as Byzantine, Romanesque, and Gothic.
-
B.
Northern Renaissance artwork
Northern Renaissance artwork comprises detailed, symbolically rich paintings, prints, and sculptures from Northern Europe (c. 1400–1600) that emphasize naturalism, intricate textures, and everyday life infused with religious and moral themes.
-
C.
Bavarian manuscript
A Bavarian manuscript is a handwritten document produced in the historical region of Bavaria, typically reflecting its local language, script traditions, and cultural or religious practices of the time.
-
D.
Glagolitic manuscript
A Glagolitic manuscript is a handwritten document produced using the Glagolitic alphabet, one of the earliest Slavic scripts, typically preserving religious, liturgical, or legal texts from the medieval Slavic cultural sphere.
-
E.
Neo-Assyrian art
Neo-Assyrian art is the visual and material culture of the Neo-Assyrian Empire (c. 911–609 BCE), characterized by monumental palace reliefs, colossal guardian figures, and finely crafted luxury objects that glorified royal power, military conquest, and divine authority.
- 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_69c6882b3a108190b3a9eb343ae4162c |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:54 p.m.