Triple
T9915974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יִשַׁי |
E185869
|
entity |
| Predicate | grandsonOf |
P27130
|
FINISHED |
| Object | Boaz |
E108456
|
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: Boaz | Statement: [יִשַׁי, grandsonOf, Boaz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boaz Context triple: [יִשַׁי, grandsonOf, Boaz]
-
A.
Boaz
Boaz is one of the two prominent bronze pillars that stood at the entrance of Solomon’s Temple in Jerusalem, as described in the Hebrew Bible.
-
B.
Boaz
Boaz is a small city in northeastern Alabama known for its outlet shopping and location atop Sand Mountain.
-
C.
Boaz
chosen
Boaz is a prominent figure in the Hebrew Bible, known as a wealthy and righteous landowner of Bethlehem who marries Ruth and becomes an ancestor of King David.
-
D.
Elimelech
Elimelech is a biblical figure from the Book of Ruth, known as Naomi’s husband who left Bethlehem for Moab during a famine and died there.
-
E.
Abinadab
Abinadab is a biblical figure mentioned in the Old Testament as one of King David’s brothers and a son of Jesse of Bethlehem.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb53d5be48190ab47e152760d5e2c |
completed | April 2, 2026, 12:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d228ae315c8190bedb2cbab0982118 |
completed | April 5, 2026, 9:17 a.m. |
Created at: March 30, 2026, 8:42 p.m.