Triple
T12211416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makaryev Monastery |
E290968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fortified monastery |
C14800
|
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: fortified monastery Context triple: [Makaryev Monastery, instanceOf, fortified monastery]
-
A.
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.
-
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.
Baroque monastery
A Baroque monastery is a religious complex characterized by dramatic, ornate architecture, rich decorative programs, and spatial designs intended to inspire awe and spiritual contemplation in accordance with Baroque artistic principles.
-
D.
fortified church
chosen
A fortified church is a religious building designed or modified with defensive features—such as walls, towers, and battlements—to protect its congregation and surrounding community during times of conflict.
-
E.
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.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.