Triple
T36186585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tractate Berakhot |
E1046862
|
entity |
| Predicate | orderInSederZeraim |
P37923
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Tractate Berakhot, orderInSederZeraim, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInSederZeraim Context triple: [Tractate Berakhot, orderInSederZeraim, 1]
-
A.
orderInSederMoed
Indicates the sequential position that an item occupies within the Seder Moed order.
-
B.
orderWithinSederNashim
Indicates the relative position or sequence of an item within the tractates of Seder Nashim in the Mishnah/Talmud ordering.
-
C.
sectionOfShulchanAruch
Indicates that one entity is a specific section or part within the larger halachic work known as the Shulchan Aruch.
-
D.
positionInMishnahOrders
chosen
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
-
E.
relationshipToShulchanAruch
Indicates the nature or type of connection that something has to the Shulchan Aruch, such as dependence on, conformity with, or derivation from it.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.