Triple

T4405637
Position Surface form Disambiguated ID Type / Status
Subject Judah son of Jacob E93726 entity
Predicate givenName P17 FINISHED
Object Judah E373707 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: Judah | Statement: [Judah son of Jacob, givenName, Judah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judah
Context triple: [Judah son of Jacob, givenName, Judah]
  • A. Yehuda chosen
    Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
  • B. Naphtali
    Naphtali is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Naphtali.
  • C. Binyamin
    Binyamin is a figure in Islamic and biblical tradition known as the younger brother of the prophet Yusuf (Joseph).
  • D. Or Yehuda
    Or Yehuda is a city in central Israel, located in the Tel Aviv District and functioning largely as a residential suburb of the Tel Aviv metropolitan area.
  • E. Edomite
    Edomite was an extinct Northwest Semitic language once spoken by the ancient Edomites in the region south of the Kingdom of Judah.
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b35489f6948190a4b2c259f64b4abf completed March 13, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5f6058f2c8190a50862d1a4607f3c completed March 14, 2026, 11:57 p.m.
Created at: March 12, 2026, 11:28 p.m.