Triple

T19081874
Position Surface form Disambiguated ID Type / Status
Subject Achbor son of Micaiah E467050 entity
Predicate kingdom P567 FINISHED
Object Judah 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: Judah | Statement: [Achbor son of Micaiah, kingdom, Judah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judah
Context triple: [Achbor son of Micaiah, kingdom, Judah]
  • A. Judah chosen
    Judah was an ancient Israelite kingdom in the southern Levant, centered around Jerusalem and prominent in biblical history.
  • B. Yehuda
    Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
  • C. Naphtali
    Naphtali is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Naphtali.
  • D. Israel ben Josef
    Israel ben Josef was a prominent 16th-century Jewish community leader and patron in Kraków, known especially as the father of the renowned rabbi Moses Isserles (the Rema).
  • E. Binyamin
    Binyamin is a figure in Islamic and biblical tradition known as the younger brother of the prophet Yusuf (Joseph).
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e2e9fccc819092c06c5da6f043ac completed April 20, 2026, 8:25 a.m.
Created at: April 10, 2026, 12:04 p.m.