Triple
T34921986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tapa Shotor |
E1007165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient monastery complex |
C36118
|
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: ancient monastery complex Context triple: [Tapa Shotor, instanceOf, ancient monastery complex]
-
A.
ancient monastic complex
chosen
An ancient monastic complex is a historically significant, self-contained religious settlement comprising monasteries, chapels, living quarters, and communal facilities where monastic communities lived, worshipped, and worked.
-
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.
underground monastic complex
An underground monastic complex is a subterranean network of chambers, corridors, and sanctuaries designed to support the communal, spiritual, and daily life of a monastic community while remaining hidden or protected beneath the earth.
-
D.
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.
-
E.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.