Triple
T19784953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | acts of David (according to 1 Chronicles 29:29) |
E475236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Hebrew historical record |
C5611
|
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: ancient Hebrew historical record Context triple: [acts of David (according to 1 Chronicles 29:29), instanceOf, ancient Hebrew historical record]
-
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.
דמות מקראית
דמות מקראית היא ישות אנושית או על־אנושית המופיעה בסיפורי התנ"ך, בעלת תפקיד נרטיבי, תיאולוגי או מוסרי במסגרת הטקסט המקראי.
-
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.
Jewish historical work
chosen
A Jewish historical work is a text that records, interprets, and reflects on the experiences, events, and developments of Jewish people and communities across time, often integrating religious, cultural, and social perspectives.
-
E.
Jewish history
Jewish history is the study of the experiences, cultures, beliefs, and transformations of Jewish people and communities from ancient times to the present across diverse regions of the world.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:49 p.m.