Triple

T18272068
Position Surface form Disambiguated ID Type / Status
Subject Levi son of Jacob E437637 entity
Predicate child P120 FINISHED
Object Kohath 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: Kohath | Statement: [Levi son of Jacob, child, Kohath]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kohath
Context triple: [Levi son of Jacob, child, Kohath]
  • A. Kohath chosen
    Kohath is a key ancestral figure in the Hebrew Bible, known as one of Levi’s sons and the forefather of the Kohathite priestly clan from which Moses and Aaron descended.
  • B. Taḥanun
    Taḥanun is a Jewish penitential prayer recited during weekday services, asking for divine mercy and forgiveness.
  • C. Shevet HaLevi
    Shevet HaLevi is a widely respected multi-volume collection of halachic responsa and rulings authored by Rabbi Shmuel HaLevi Wosner, influential in contemporary Jewish law.
  • D. Ithamar
    Ithamar is a biblical figure, a son of Aaron who served as a priest in ancient Israel.
  • E. Huelel
    Huelel is the self-designated name (endonym) used by the Esselen people, an Indigenous group native to the central coast of California.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5004f0e7c8190a7206e193012a2d3 completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 10:34 a.m.