Triple

T16359198
Position Surface form Disambiguated ID Type / Status
Subject Deuteronomy 34 E397265 entity
Predicate mentionsPlace P831 FINISHED
Object Manasseh E152129 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: [Deuteronomy 34, mentionsPlace, Manasseh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manasseh
Context triple: [Deuteronomy 34, mentionsPlace, Manasseh]
  • A. Manasseh chosen
    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
    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. Pekah
    Pekah was a king of the northern Kingdom of Israel in the 8th century BCE, known for his reign during a period of political instability and conflict with Assyria.
  • D. 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.
  • E. Josiah
    Josiah was a king of Judah in the Hebrew Bible, known for his religious reforms and efforts to restore the worship of Yahweh.
  • 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_69d87f2778dc8190aa95c7572db127e6 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2fad1859c819082b47bf9d7fabd9f completed April 18, 2026, 3:30 a.m.
NED1 Entity disambiguation (via context triple) batch_6a002dbce2508190b655de87f48e841e completed May 10, 2026, 7:03 a.m.
Created at: April 10, 2026, 5:07 a.m.