Triple
T4852504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ish-bosheth |
E108448
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Abinadab son of Saul |
E114398
|
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: Abinadab son of Saul | Statement: [Ish-bosheth, relative, Abinadab son of Saul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abinadab son of Saul Context triple: [Ish-bosheth, relative, Abinadab son of Saul]
-
A.
Abinadab
chosen
Abinadab is a son of King Saul mentioned in the Hebrew Bible, known for dying alongside his father in battle against the Philistines.
-
B.
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.
-
C.
Abinoam
Abinoam is a biblical figure mentioned in the Old Testament as the father of the Israelite military leader Barak.
-
D.
Ehud
Ehud is a biblical judge and deliverer of Israel known for assassinating the Moabite king Eglon in the Book of Judges.
-
E.
Othniel
Othniel is a biblical figure regarded as the first judge of Israel, known for delivering the Israelites from oppression in the Book of Judges.
- 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_69bd440a89548190a5f14ba6da6b97dc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d39a4cc81908e27f587729225b0 |
completed | March 20, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be5ce33db08190b44b5b0c21d2b850 |
completed | March 21, 2026, 8:54 a.m. |
Created at: March 20, 2026, 1:26 p.m.