Triple
T31802345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prüm Abbey |
E811774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Carolingian religious center |
C25345
|
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: Carolingian religious center Context triple: [Prüm Abbey, instanceOf, Carolingian religious center]
-
A.
Christian monastic center
A Christian monastic center is a religious community and physical complex where monks or nuns live under a shared rule of life devoted to prayer, worship, work, and spiritual formation.
-
B.
former Benedictine monastery
A former Benedictine monastery is a religious complex once inhabited and operated by Benedictine monks, now no longer functioning as an active Benedictine community but often preserved or repurposed for other uses.
-
C.
Christian monastic complex
chosen
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.
-
D.
Carolingian architecture
Carolingian architecture is a style of early medieval European building, promoted by the Carolingian dynasty (8th–9th centuries), that revived and adapted elements of ancient Roman and early Christian architecture to express imperial power and religious reform.
-
E.
Benedictine archabbey
A Benedictine archabbey is a principal monastery of the Benedictine Order that holds preeminent status over other abbeys in its region, led by an archabbot and serving as a spiritual, administrative, and often cultural center.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:42 p.m.