Triple
T3175635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josiah |
E66458
|
entity |
| Predicate | grandfather |
P979
|
FINISHED |
| Object | Manasseh |
E143500
|
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: Manasseh | Statement: [Josiah, grandfather, Manasseh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Manasseh Context triple: [Josiah, grandfather, Manasseh]
-
A.
Manasseh
Manasseh is one of the tribes of Israel, traditionally descended from Joseph’s son Manasseh and associated with territory on both sides of the Jordan River.
-
B.
Manasseh, king of Judah
chosen
Manasseh, king of Judah, was a biblical monarch known for his long reign, notorious idolatry and later repentance as recounted in the Hebrew Bible.
-
C.
Josiah
Josiah was a king of Judah in the Hebrew Bible, known for his religious reforms and efforts to restore the worship of Yahweh.
-
D.
Jehoahaz
Jehoahaz was a king of Judah and son of Josiah who briefly reigned before being deposed by the Egyptian Pharaoh Necho II.
-
E.
King of Judah
The King of Judah was the monarchic ruler of the ancient southern Hebrew kingdom of Judah, centered in Jerusalem, during the period of the divided monarchy and subsequent vassalage to foreign empires.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada671e6848190a683eec1519b9268 |
completed | March 8, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b24b66b3e081908e8ea11d9b36e50a |
completed | March 12, 2026, 5:13 a.m. |
Created at: March 8, 2026, 3:06 p.m.