Triple
T4887598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malchi-shua |
E109474
|
entity |
| Predicate | diedAlongside |
P46030
|
FINISHED |
| Object | Abinadab |
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 | Statement: [Malchi-shua, diedAlongside, Abinadab]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abinadab Context triple: [Malchi-shua, diedAlongside, Abinadab]
-
A.
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.
-
B.
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.
-
C.
Abinoam
Abinoam is a biblical figure mentioned in the Old Testament as the father of the Israelite military leader Barak.
-
D.
Shem
Shem is a biblical figure regarded as one of Noah’s sons and traditionally considered an ancestor of the Semitic peoples.
-
E.
Bethuel
Bethuel is a biblical figure from the Book of Genesis, known as the father of Laban and Rebekah and a descendant of Abraham’s family line.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7163789c81909d5c7d0f6756ca58 |
completed | March 20, 2026, 4:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fbba1688190a812cac53992dece |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:28 p.m.