Triple
T19784368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esh-baal |
E475220
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Ishbaal |
—
|
NE NERFINISHED |
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: Ishbaal | Statement: [Esh-baal, hasAlternativeName, Ishbaal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ishbaal Context triple: [Esh-baal, hasAlternativeName, Ishbaal]
-
A.
Eshbaal
Eshbaal is a biblical figure mentioned in the Hebrew Bible, known primarily as a son of Ahinoam daughter of Ahimaaz.
-
B.
Ish-bosheth
chosen
Ish-bosheth is a biblical figure, a son of King Saul who briefly ruled part of Israel in opposition to David after Saul’s death.
-
C.
Cushan-Rishathaim
Cushan-Rishathaim is a foreign king mentioned in the biblical Book of Judges as an oppressor of Israel whom God delivered into the hands of the judge Othniel.
-
D.
Shaul
Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
-
E.
Zimri
Zimri was a short-reigning king of the northern Kingdom of Israel, known from the Hebrew Bible for seizing the throne through a coup and then dying in a palace fire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538715b8819080c6930e7d16ab58 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.