Triple
T11177632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arakhin |
E264452
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Seder Kodashim |
E906786
|
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: Seder Kodashim | Statement: [Arakhin, partOf, Seder Kodashim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seder Kodashim Context triple: [Arakhin, partOf, Seder Kodashim]
-
A.
Seder Kodashim
chosen
Seder Kodashim is the order of the Mishnah and Talmud that deals primarily with Temple service, sacrificial offerings, and related laws of holiness.
-
B.
Seder Zeraim
Seder Zeraim is the first order of the Mishnah, primarily dealing with agricultural laws and blessings in Jewish law.
-
C.
Seder Tohorot
Seder Tohorot is the sixth order of the Mishnah, dealing primarily with the complex laws of ritual purity and impurity in Jewish law.
-
D.
Seder Nezikin
Seder Nezikin is one of the six orders of the Mishnah and Talmud, primarily dealing with civil and criminal law, damages, and judicial procedures in Jewish law.
-
E.
Seder Moed
Seder Moed is the section of rabbinic literature that deals primarily with Jewish festivals, Sabbaths, and related laws of sacred time.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8987e1081909b28a0bdb866beae |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4cc1ed3d0819089c6885f21350298 |
completed | April 19, 2026, 12:35 p.m. |
Created at: April 8, 2026, 9:29 p.m.