Triple
T13682038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | לֵוִי |
E328025
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Kohath |
E328026
|
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: Kohath | Statement: [לֵוִי, child, Kohath]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kohath Context triple: [לֵוִי, 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.
Ithamar
Ithamar is a biblical figure, a son of Aaron who served as a priest in ancient Israel.
-
C.
Zorah
Zorah was an ancient town in the territory of the Tribe of Dan, known from the Hebrew Bible as the hometown of Samson.
-
D.
Issachar
Issachar is one of the twelve sons of Jacob in the Hebrew Bible and the traditional ancestor of the Israelite Tribe of Issachar.
-
E.
Iscah
Iscah is a minor biblical figure mentioned in the Book of Genesis, traditionally identified by some commentators with Sarai (Sarah), the wife of Abraham.
- 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_69f7944551b481909833cdcff198889c |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:53 p.m.