Triple

T3720264
Position Surface form Disambiguated ID Type / Status
Subject Coniah E81620 entity
Predicate kingdom P567 FINISHED
Object Judah E93726 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: [Coniah, kingdom, Judah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judah
Context triple: [Coniah, kingdom, Judah]
  • A. Yehuda
    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. 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.
  • D. Edomite
    Edomite was an extinct Northwest Semitic language once spoken by the ancient Edomites in the region south of the Kingdom of Judah.
  • E. Judah son of Jacob chosen
    Judah son of Jacob is a prominent biblical patriarch, one of the twelve sons of Jacob, and the ancestral figure from whom the Tribe of Judah and the royal Davidic line are traditionally believed to descend.
  • 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_69ad8b1b7ef081908d2d381bbf54985a completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adca9b5ca8819094299fffc02606ce completed March 8, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4ce184c9c8190813ce589c48007c1 completed March 14, 2026, 2:55 a.m.
Created at: March 8, 2026, 3:34 p.m.