Triple
T21529443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hilchot Beit HaBechirah |
E531189
|
entity |
| Predicate | sequenceInMishnehTorah |
P71959
|
FINISHED |
| Object | one of the opening sections of Sefer Avodah |
—
|
LITERAL 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: one of the opening sections of Sefer Avodah | Statement: [Hilchot Beit HaBechirah, sequenceInMishnehTorah, one of the opening sections of Sefer Avodah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceInMishnehTorah Context triple: [Hilchot Beit HaBechirah, sequenceInMishnehTorah, one of the opening sections of Sefer Avodah]
-
A.
positionInMishnehTorah
chosen
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
-
B.
positionInMishnahOrders
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
-
C.
appearsInTractate
Indicates that one entity (such as a topic, law, or passage) is contained within or discussed in a particular tractate.
-
D.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
E.
sectionOfShulchanAruch
Indicates that one entity is a specific section or part within the larger halachic work known as the Shulchan Aruch.
- F. None of above.
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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee88539d948190a5e3acc25c1e292e |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.