Triple
T20320496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arimathea (traditional identification) |
E492194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical geography topic |
C35918
|
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: biblical geography topic Context triple: [Arimathea (traditional identification), instanceOf, biblical geography topic]
-
A.
biblical toponym
chosen
A biblical toponym is a place name that appears in the texts of the Bible, often carrying historical, religious, and cultural significance within the biblical narrative.
-
B.
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.
-
C.
biblical studies resource
A biblical studies resource is a tool, text, or digital aid designed to support the scholarly and devotional study, interpretation, and teaching of the Bible and its historical, literary, and theological contexts.
-
D.
geographical work
A geographical work is a creative or scholarly resource that represents, analyzes, or describes the Earth's surface, places, spatial relationships, or geographic phenomena.
-
E.
biblical kingdom
A biblical kingdom is a divinely oriented realm or nation, often ruled by a monarch, whose identity, laws, and destiny are framed and interpreted through the narratives, covenants, and theological themes of the Bible.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:20 a.m.