Triple
T19075931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerubbaal |
E466901
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Joash |
—
|
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: Joash | Statement: [Jerubbaal, father, Joash]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joash Context triple: [Jerubbaal, father, Joash]
-
A.
Joash
chosen
Joash is a biblical figure from the Old Testament, known primarily as the father of Gideon, the judge and military leader of Israel.
-
B.
King Joash of Israel
King Joash of Israel was a monarch of the northern Kingdom of Israel in the 9th century BCE, noted in the Hebrew Bible for his military conflicts with Aram-Damascus and Judah and his interactions with the prophet Elisha.
-
C.
Adonijah
Adonijah was a son of King David in the Hebrew Bible who attempted to claim the throne of Israel before Solomon’s succession.
-
D.
Uzziah
Uzziah was a long-reigning king of Judah in the Hebrew Bible, remembered for his military success, economic prosperity, and eventual downfall after being struck with leprosy.
-
E.
Ish-bosheth
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.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e49c7c8190b6ce7b918086b23c |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 10, 2026, 12:04 p.m.