Triple

T14630072
Position Surface form Disambiguated ID Type / Status
Subject Korah E343457 entity
Predicate distinguishedFrom P1612 FINISHED
Object Korah son of Izhar E81193 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: Korah son of Izhar | Statement: [Korah, distinguishedFrom, Korah son of Izhar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korah son of Izhar
Context triple: [Korah, distinguishedFrom, Korah son of Izhar]
  • A. Korah
    Korah is a minor biblical figure mentioned in the Book of Genesis as a descendant of Esau and part of the Edomite lineage.
  • B. Korah chosen
    Korah is a biblical figure known for leading a rebellion against Moses and Aaron during the Israelites’ wilderness journey.
  • C. Nadab
    Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
  • D. Nadab
    Nadab was a king of the northern Kingdom of Israel in the Hebrew Bible, known as the son and short-reigning royal heir of Jeroboam I.
  • E. Dathan
    Dathan is a biblical figure known as one of the leaders who rebelled against Moses and Aaron during the Israelites’ wilderness journey.
  • 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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb4a912248190a3df7f821395c776 completed April 14, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb7ab30c8190af49268b6f93aeb1 completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:26 a.m.