Triple
T9310709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbinic literature |
E223998
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Sifre |
E102803
|
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: Sifre | Statement: [Rabbinic literature, hasPart, Sifre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sifre Context triple: [Rabbinic literature, hasPart, Sifre]
-
A.
Sifra
Sifra is a classical rabbinic midrash on the Book of Leviticus that systematically expounds its legal (halakhic) passages.
-
B.
Sifre Zuta
chosen
Sifre Zuta is a lesser-known tannaitic midrashic work that offers halakhic interpretation and commentary on parts of the Hebrew Bible, traditionally associated with the school of Rabbi Akiva.
-
C.
Kirfi
Kirfi is a West Chadic language spoken in parts of northern Nigeria.
-
D.
Sifung
Sifung is a traditional bamboo flute central to the folk music and cultural expression of the Bodo people of Northeast India.
-
E.
Sifayuan
Sifayuan is the Mandarin name for Taiwan’s Judicial Yuan, the constitutional body responsible for overseeing the judiciary and interpreting the constitution.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ac17488190aa6acf7a61420632 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0e39d03508190aca18600c33bfdd8 |
completed | April 4, 2026, 10:10 a.m. |
Created at: March 30, 2026, 7:37 p.m.