Triple
T23934901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land of Zebulun |
E602606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of ancient Israel |
C34226
|
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: region of ancient Israel Context triple: [Land of Zebulun, instanceOf, region of ancient Israel]
-
A.
region of ancient Palestine
chosen
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.
-
B.
region of ancient Mesopotamia
A region of ancient Mesopotamia is a geographically defined area within the broader Mesopotamian landscape, characterized by shared political, cultural, and economic features during a specific historical period.
-
C.
region of Jordan
A region of Jordan is a defined geographic and administrative area within the country, characterized by shared physical, cultural, or economic features that distinguish it from other parts of Jordan.
-
D.
Israeli settlement region
An Israeli settlement region is a geographically defined area in territories occupied by Israel where Israeli civilian communities are established and administered under Israeli authority, often amid international dispute and complex legal and political status.
-
E.
region of ancient Cilicia
A region of ancient Cilicia is a historically defined geographic area within the larger territory of Cilicia, characterized by its distinct political, cultural, or administrative identity in antiquity.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9 p.m.