Triple

T13682085
Position Surface form Disambiguated ID Type / Status
Subject Kohath E328026 entity
Predicate scripturalGenealogy P36142 FINISHED
Object Levi–Kohath–Amram–Aaron E446274 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: Levi–Kohath–Amram–Aaron | Statement: [Kohath, scripturalGenealogy, Levi–Kohath–Amram–Aaron]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Levi–Kohath–Amram–Aaron
Context triple: [Kohath, scripturalGenealogy, Levi–Kohath–Amram–Aaron]
  • A. Nachshon ben Amminadab
    Nachshon ben Amminadab is a biblical figure from the Book of Exodus, traditionally revered as the first Israelite to step into the Red Sea in an act of pioneering faith and courage.
  • B. Amram chosen
    Amram is a biblical figure from the Hebrew Bible, known primarily as the father of Moses, Aaron, and Miriam and a descendant of Levi.
  • C. 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.
  • D. Nadab
    Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
  • E. Aharon
    Aharon is a masculine given name of Hebrew origin, traditionally associated with the biblical figure Aaron and widely used in Jewish communities.
  • 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_69d8076f1fa8819094664a59b55010df completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc66e75188190a9e82fdc5eb26513 completed April 12, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79d4a4a50819098bd4348eba19ee7 completed May 3, 2026, 7:08 p.m.
Created at: April 9, 2026, 9:53 p.m.