Triple
T30498703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Succoth |
E776078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | populated place in the Hebrew Bible |
C14559
|
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: populated place in the Hebrew Bible Context triple: [Succoth, instanceOf, populated place in the Hebrew Bible]
-
A.
populated place in Israel
A populated place in Israel is a geographically defined area within the State of Israel where people live, such as a city, town, village, kibbutz, or moshav, recognized for administrative, residential, or communal purposes.
-
B.
location mentioned in the Hebrew Bible
chosen
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.
-
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.
Hebrew city
A Hebrew city is an urban settlement historically or presently inhabited by Hebrew-speaking or Jewish communities, characterized by its cultural, religious, and social institutions rooted in Hebrew and Jewish traditions.
-
E.
region of ancient Palestine
A region of ancient Palestine is a geographically and culturally distinct area within the historical land of Palestine, defined by its political boundaries, settlements, and role in biblical and Near Eastern history.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:14 p.m.