Triple
T23995711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Cross Armenian Catholic Church Zalka (Greater Beirut) |
E605183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian religious landmark |
C1820
|
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 landmark Context triple: [Holy Cross Armenian Catholic Church Zalka (Greater Beirut), instanceOf, Christian religious landmark]
-
A.
Christian holy place
chosen
A Christian holy place is a location—such as a church, chapel, shrine, or site of religious significance—set apart for worship, prayer, and encounters with the divine within the Christian tradition.
-
B.
religious site
A religious site is a designated place or structure where individuals or communities engage in worship, rituals, and other practices associated with their faith or spiritual beliefs.
-
C.
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.
-
D.
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.
-
E.
religious building
A religious building is a structure specifically designed and used for worship, rituals, and other activities associated with a particular faith or spiritual tradition.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:38 p.m.