Triple
T4935583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abimelech |
E110803
|
entity |
| Predicate | sonOf |
P25213
|
FINISHED |
| Object | Jerubbaal |
E466901
|
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: Jerubbaal | Statement: [Abimelech, sonOf, Jerubbaal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jerubbaal Context triple: [Abimelech, sonOf, Jerubbaal]
-
A.
Jerubbaal
chosen
Jerubbaal is an alternate name for Gideon, the biblical judge and military leader who delivered Israel from Midianite oppression.
-
B.
Jephthah
Jephthah is a biblical judge of Israel known for his military leadership against the Ammonites and his tragic vow involving his daughter.
-
C.
Shamgar
Shamgar is a minor biblical judge and warrior mentioned in the Book of Judges, known for defeating a large number of Philistines with an oxgoad.
-
D.
Jephta
Jephta is a 17th-century Dutch tragedy by Joost van den Vondel that dramatizes the biblical story of Jephthah and his fateful vow.
-
E.
Benaiah
Benaiah was a prominent Israelite warrior and commander under King David and King Solomon, renowned for his bravery and loyalty in biblical accounts.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706825188190b854dca5ca2f9db6 |
completed | March 20, 2026, 4:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be77b74c748190a995a26f45b79ee9 |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:30 p.m.