Triple
T14060557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uriah son of Shemaiah |
E338332
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object |
Shemaiah
Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
|
E1077952
|
NE FINISHED |
How this triple was built (4 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: Shemaiah | Statement: [Uriah son of Shemaiah, father, Shemaiah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shemaiah Context triple: [Uriah son of Shemaiah, father, Shemaiah]
-
A.
Shimeah
Shimeah is a biblical figure mentioned in the Hebrew Bible, known primarily as an alternative name for Shammah.
-
B.
Azariah
Azariah is a biblical figure portrayed as one of the three youths delivered by God from the fiery furnace in the Book of Daniel and related deuterocanonical additions.
-
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.
Hilkiah
Hilkiah is a biblical figure known as the father of the prophet Jeremiah and, in some traditions, identified with the high priest who discovered the Book of the Law in the Temple.
-
E.
Yehoyaqim
Yehoyaqim is a king of Judah mentioned in the Hebrew Bible, known for his reign during the late 7th to early 6th century BCE amid rising Babylonian power.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Shemaiah Triple: [Uriah son of Shemaiah, father, Shemaiah]
Generated description
Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Shemaiah Target entity description: Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
-
A.
Shimeah
Shimeah is a biblical figure mentioned in the Hebrew Bible, known primarily as an alternative name for Shammah.
-
B.
Azariah
Azariah is a biblical figure portrayed as one of the three youths delivered by God from the fiery furnace in the Book of Daniel and related deuterocanonical additions.
-
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.
Hilkiah
Hilkiah is a biblical figure known as the father of the prophet Jeremiah and, in some traditions, identified with the high priest who discovered the Book of the Law in the Temple.
-
E.
Yehoyaqim
Yehoyaqim is a king of Judah mentioned in the Hebrew Bible, known for his reign during the late 7th to early 6th century BCE amid rising Babylonian power.
- F. None of above. chosen
Provenance (5 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5686f51c81908c33143ecbaae83d |
completed | April 14, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb6654850819083262f3fb981eb1a |
completed | May 7, 2026, 3:57 p.m. |
| NEDg | Description generation | batch_69fcc4fa09448190b662af829712e657 |
completed | May 7, 2026, 4:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fcc5d162c081908750fed589ed2d69 |
completed | May 7, 2026, 5:03 p.m. |
Created at: April 9, 2026, 10:21 p.m.