Triple
T36395314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sant Pere de Casserres |
E896457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanesque Benedictine monastery |
C30116
|
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: Romanesque Benedictine monastery Context triple: [Sant Pere de Casserres, instanceOf, Romanesque Benedictine monastery]
-
A.
Romanesque monastery
chosen
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.
-
B.
Cistercian monastery
A Cistercian monastery is a self-contained religious community following the Cistercian Order’s strict observance of the Rule of St. Benedict, characterized by simplicity, manual labor, and communal prayer.
-
C.
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.
-
D.
former Cistercian monastery
A former Cistercian monastery is a religious complex originally founded and occupied by the Cistercian order of monks or nuns, which has since lost its monastic function and may now serve secular, cultural, or other religious purposes.
-
E.
Roman Catholic monastery
A Roman Catholic monastery is a religious community where monks or nuns live a cloistered life of prayer, work, and communal worship according to the rules of a specific Catholic order.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.