Triple
T4852485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ish-bosheth |
E108448
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ish-bosheth |
E108448
|
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: Ish-bosheth | Statement: [Ish-bosheth, givenName, Ish-bosheth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ish-bosheth Context triple: [Ish-bosheth, givenName, Ish-bosheth]
-
A.
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.
-
B.
Jehozadak
Jehozadak is a biblical priestly figure known primarily as the father of Joshua the high priest who returned with the Jewish exiles from Babylon.
-
C.
Mephibosheth
Mephibosheth is a biblical figure, the disabled son of Jonathan and grandson of King Saul, known for receiving unexpected kindness and protection from King David.
-
D.
Rehoboam
Rehoboam was a king of ancient Judah, best known for his harsh policies that led to the division of the united monarchy of Israel into the northern and southern kingdoms.
-
E.
Adonijah
Adonijah was a son of King David in the Hebrew Bible who attempted to claim the throne of Israel before Solomon’s succession.
- 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.