Triple
T37559766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman |
E933785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval European style |
C66191
|
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: medieval European style Context triple: [Norman, instanceOf, medieval European style]
-
A.
medieval architectural style
A medieval architectural style is a historically rooted design tradition characterized by features such as thick stone walls, arches, vaults, and ornamental detailing that reflect the cultural, religious, and technological contexts of the Middle Ages.
-
B.
medieval charm
A medieval charm is a small, often inscribed object or spoken formula believed to harness supernatural or divine power for protection, healing, or influencing events in accordance with medieval beliefs and practices.
-
C.
medieval music style
A medieval music style is a historically rooted musical idiom characterized by modal melodies, monophonic or early polyphonic textures, and performance practices typical of European music from roughly the 5th to the 15th century.
-
D.
medieval era
The medieval era is a historical period roughly spanning the 5th to the 15th century in Europe, characterized by feudal societies, the dominance of the Catholic Church, and the gradual emergence of towns, universities, and nation-states.
-
E.
medieval art
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.
- F. None of above. chosen
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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.