Triple
T13378682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomer |
E319257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nation in the Hebrew Bible |
C21979
|
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: nation in the Hebrew Bible Context triple: [Gomer, instanceOf, nation in the Hebrew 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.
event in the Hebrew Bible
An event in the Hebrew Bible is a narrated occurrence—historical, theological, or symbolic—in which God’s purposes unfold through actions, experiences, or interventions in the lives of individuals or communities.
-
C.
Ancient Israelite
An Ancient Israelite is a member of the historical people and culture of Israel in the ancient Near East, characterized by a shared ethnic identity, language (Hebrew), religious traditions centered on Yahweh, and social life organized around tribes and later monarchies.
-
D.
Semitic state
chosen
A Semitic state is a political entity historically or culturally rooted in Semitic-speaking peoples, characterized by shared linguistic, ethnic, and often religious traditions originating in the ancient Near East.
-
E.
Israelite tribal subdivision
An Israelite tribal subdivision is a smaller kinship-based unit within one of the twelve tribes of ancient Israel, often organized by clan or family lineage for social, military, and territorial purposes.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:33 p.m.