Triple
T31017297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altenmünster site |
E790356
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early medieval monastic site |
C29712
|
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: early medieval monastic site Context triple: [Altenmünster site, instanceOf, early medieval monastic site]
-
A.
medieval monastic site
A medieval monastic site is a religious complex, typically enclosed and self-sufficient, where monks or nuns lived, worshipped, worked, and followed a regulated spiritual routine during the Middle Ages.
-
B.
early medieval site
chosen
An early medieval site is an archaeological location dating roughly from the 5th to the 11th century CE that preserves material evidence of social, political, economic, and religious life during the early Middle Ages.
-
C.
Romanesque monastery
A Romanesque monastery is a medieval monastic complex characterized by massive stone construction, rounded arches, barrel or groin vaults, and a cloister-centered layout designed for communal religious life, prayer, and self-sufficiency.
-
D.
ancient monastic complex
An ancient monastic complex is a historically significant, self-contained religious settlement comprising monasteries, chapels, living quarters, and communal facilities where monastic communities lived, worshipped, and worked.
-
E.
Christian monastic complex
A Christian monastic complex is an integrated group of religious buildings and spaces—such as a church, cloister, dormitories, refectory, and work areas—designed to support the communal, spiritual, and daily life of monks or nuns.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.