Triple
T14835798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayravank Monastery |
E348826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian religious complex |
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: Christian religious complex Context triple: [Hayravank Monastery, instanceOf, Christian religious complex]
-
A.
Christian church complex
A Christian church complex is an integrated group of religious buildings and spaces, typically including a main church, auxiliary chapels, administrative and community facilities, and associated outdoor areas, dedicated to Christian worship, ministry, and communal life.
-
B.
Christian religious institution
A Christian religious institution is an organized body, such as a church or denomination, that structures, practices, and governs the communal worship, doctrine, and spiritual life of Christians.
-
C.
religious structure
A religious structure is a building or space specifically designed and used for worship, rituals, and other activities associated with a particular faith or spiritual tradition.
-
D.
historical religious institution
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
E.
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.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:52 a.m.