Triple

T6687216
Position Surface form Disambiguated ID Type / Status
Subject Manasseh E152129 entity
Predicate namedAfter P63 FINISHED
Object Manasseh son of Joseph 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 son of Joseph | Statement: [Manasseh, namedAfter, Manasseh son of Joseph]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manasseh son of Joseph
Context triple: [Manasseh, namedAfter, Manasseh son of Joseph]
  • A. 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.
  • B. 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.
  • 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. Amon, king of Judah
    Amon, king of Judah, was a late 7th-century BCE monarch of the Kingdom of Judah whose brief and idolatrous reign ended in assassination, leading to the succession of his son Josiah.
  • E. Jozue
    Jozue is a given name and form of the biblical name Joshua, used in various European languages and traditions.
  • 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_69c687f9977c819097e7f5ada4fe522e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b14e58708190a4ba8ff1c085f160 completed March 27, 2026, 4:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6f7b31fa0819089c4debbbbce9d22 completed March 27, 2026, 9:33 p.m.
Created at: March 27, 2026, 2:04 p.m.