Triple
T20054897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chileab |
E499301
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Shephatiah |
—
|
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: Shephatiah | Statement: [Chileab, sibling, Shephatiah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shephatiah Context triple: [Chileab, sibling, Shephatiah]
-
A.
Shephatiah
chosen
Shephatiah is one of the sons of King David mentioned in the Hebrew Bible.
-
B.
Seraiah
Seraiah is a biblical figure mentioned in the Hebrew Bible, known as a priestly ancestor in the lineage leading to Jehozadak.
-
C.
Berechiah
Berechiah is a biblical figure mentioned in the Hebrew Bible as part of the priestly and prophetic lineage associated with the prophet Zechariah.
-
D.
Shealtiel
Shealtiel is a biblical figure known primarily as a descendant of King Jehoiachin and an ancestor of Zerubbabel in the Davidic royal line.
-
E.
Shemariah
Shemariah is a biblical figure mentioned in genealogical records as a descendant within the line associated with Mahalath.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66332b300819097f5dca1636e5822 |
completed | April 20, 2026, 5:32 p.m. |
Created at: April 11, 2026, 3:38 p.m.