Triple
T19850488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohen |
E476978
|
entity |
| Predicate | pluralFormHebrew |
P5088
|
FINISHED |
| Object | Kohanim |
—
|
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: Kohanim | Statement: [Kohen, pluralFormHebrew, Kohanim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kohanim Context triple: [Kohen, pluralFormHebrew, Kohanim]
-
A.
Kohen
chosen
Kohen is a variant spelling of "Cohen," referring to a member of the Jewish priestly class traditionally descended from Aaron.
-
B.
Tannaim
The Tannaim were early rabbinic sages of roughly the 1st–3rd centuries CE whose teachings form the core of the Mishnah and laid the foundation for classical Jewish law and tradition.
-
C.
Geonim
The Geonim were the heads of the great Talmudic academies in Babylonia during the early medieval period, serving as the supreme rabbinic authorities and shaping the development of Jewish law and tradition.
-
D.
Savoraim
The Savoraim were Jewish Talmudic scholars who succeeded the Amoraim and are traditionally credited with editing, organizing, and finalizing the Babylonian Talmud.
-
E.
Aron ha-Kodesh
Aron ha-Kodesh is the ornate Torah ark in a synagogue where the sacred Torah scrolls are stored.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65867b5408190bbd12ca567c4705f |
completed | April 20, 2026, 4:46 p.m. |
Created at: April 10, 2026, 1:51 p.m.