Triple
T14630026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalam |
E343456
|
entity |
| Predicate | hasMother |
P1909
|
FINISHED |
| Object | Aholibamah |
E1109483
|
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: Aholibamah | Statement: [Jalam, hasMother, Aholibamah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aholibamah Context triple: [Jalam, hasMother, Aholibamah]
-
A.
Aholibamah
chosen
Aholibamah is a biblical figure mentioned in the Book of Genesis, known as one of Esau’s wives and a matriarch of Edomite clans.
-
B.
Elisheba
Elisheba is a Hebrew given name of biblical origin, traditionally understood to mean “God is my oath” or “God is satisfaction.”
-
C.
Zilpah
Zilpah is a biblical figure who served as Leah’s maidservant and bore two of Jacob’s sons, Gad and Asher.
-
D.
Naamah the Ammonite
Naamah the Ammonite is a biblical figure known as the Ammonite wife of King Solomon and the mother of King Rehoboam of Judah.
-
E.
Shelomith
Shelomith is a lesser-known biblical figure mentioned in the Hebrew Bible as a member of King Rehoboam’s family lineage.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a912248190a3df7f821395c776 |
completed | April 14, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde16e85488190b0dcc2ccd2f5df4d |
completed | May 8, 2026, 1:13 p.m. |
Created at: April 10, 2026, 1:26 a.m.