Triple
T8280539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | people of Lot |
E193658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community mentioned in the Bible |
C5276
|
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: community mentioned in the Bible Context triple: [people of Lot, instanceOf, community mentioned in the Bible]
-
A.
location mentioned in the Hebrew Bible
A "location mentioned in the Hebrew Bible" is any geographically identifiable place—such as a city, region, landmark, or territory—explicitly referenced within the canonical texts of the Hebrew Scriptures.
-
B.
church mentioned in the Book of Revelation
A church mentioned in the Book of Revelation is a Christian congregation or community addressed in Revelation’s letters, symbolizing both a historical local assembly and a spiritual type with specific strengths, weaknesses, and prophetic significance.
-
C.
biblical city
A biblical city is an urban settlement referenced in the Bible, often serving as the setting for religious events, narratives, and teachings within the biblical tradition.
-
D.
New Testament location
A New Testament location is any geographical place, region, or city referenced in the New Testament that provides historical and narrative context for its events and teachings.
-
E.
biblical group
chosen
A biblical group is a collection of individuals or entities in the Bible that are associated by a common identity, purpose, lineage, or role within the biblical narrative.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:51 p.m.