Triple
T1044786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ithream |
E22551
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object | Eglah |
E22551
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Eglah | Statement: [Ithream, mother, Eglah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eglah Context triple: [Ithream, mother, Eglah]
-
A.
Eglah
chosen
Eglah is a lesser-known wife of the biblical King David, mentioned among the mothers of his sons in the Hebrew Bible.
-
B.
Gezerot
Gezerot are rabbinic decrees in Judaism enacted as protective safeguards around biblical law or to address communal needs.
-
C.
Libnah
Libnah was a woman of the royal family of Judah, known primarily as the wife of King Josiah and the mother of King Zedekiah.
-
D.
Haran
Haran is an ancient city in northern Mesopotamia known from the Hebrew Bible as a key dwelling place of the patriarch Abraham before his journey to Canaan.
-
E.
Shechem
Shechem was an important ancient city in the central highlands of Canaan, serving as a significant political and religious center in biblical times.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b84937688190a5899af2104002df |
completed | March 1, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac3bc97dec81909b6ad48e3f203923 |
completed | March 7, 2026, 2:52 p.m. |
Created at: March 1, 2026, 7:42 p.m.