Triple
T13378382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divided Monarchy period |
E319249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | period of ancient Israelite history |
C138
|
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: period of ancient Israelite history Context triple: [Divided Monarchy period, instanceOf, period of ancient Israelite history]
-
A.
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.
-
B.
Old Testament event
An Old Testament event is a significant occurrence or narrative described in the Hebrew Bible that shapes the religious, historical, and theological context of ancient Israel.
-
C.
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.
-
D.
historical period
chosen
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
E.
rabbinic era
The rabbinic era is the historical period, roughly from the 1st to the 7th century CE, during which rabbinic Judaism developed its foundational texts, institutions, and legal traditions following the destruction of the Second Temple.
- 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.