Triple
T23356666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Testament tradition of Bethany beyond the Jordan |
E593069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian holy site tradition |
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 holy site tradition Context triple: [New Testament tradition of Bethany beyond the Jordan, instanceOf, Christian holy site tradition]
-
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.
Islamic holy site
An Islamic holy site is a place of religious significance in Islam, revered for its association with Allah, the Prophet Muhammad, or key events and figures in Islamic history, and used for worship, pilgrimage, and spiritual reflection.
-
C.
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.
-
D.
religious heritage
Religious heritage is the collection of beliefs, practices, artifacts, sites, and traditions passed down through generations that embody the historical and cultural legacy of a faith community.
-
E.
Jewish pilgrimage site
A Jewish pilgrimage site is a location of religious and historical significance in Judaism to which individuals or communities travel, traditionally or in contemporary practice, for prayer, commemoration, and spiritual connection.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:28 p.m.