Triple
T10371952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goshavank Monastery |
E244404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval monastic complex |
C22222
|
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 monastic complex Context triple: [Goshavank Monastery, instanceOf, medieval monastic complex]
-
A.
medieval monastic site
chosen
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.
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.
-
C.
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.
-
D.
medieval religious house
A medieval religious house is a community-based institution, such as a monastery, nunnery, or friary, where members of a religious order live under a rule, worship, and manage spiritual, educational, and economic activities.
-
E.
Benedictine complex
A Benedictine complex is an architectural ensemble centered around a Benedictine monastery, typically including a church, cloister, living quarters, workspaces, and communal facilities arranged to support monastic life according to the Rule of Saint Benedict.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:01 p.m.