Triple
T11146925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bekhorot |
E263691
|
entity |
| Predicate | hasBabylonianTalmudPagesApprox |
P98050
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Bekhorot, hasBabylonianTalmudPagesApprox, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBabylonianTalmudPagesApprox Context triple: [Bekhorot, hasBabylonianTalmudPagesApprox, 60]
-
A.
hasGemara
Indicates that an entity possesses, includes, or is associated with a Gemara (a Talmudic text or study component).
-
B.
hasJerusalemTalmud
Indicates that an entity possesses, is associated with, or is characterized by the Jerusalem Talmud.
-
C.
hasNoBavliGemaraForMostTractates
Indicates that there is no Babylonian Talmud (Bavli) Gemara text available for the majority of the tractates in question.
-
D.
containsParshiyot
Indicates that one textual or structural unit (such as a Torah scroll or section) includes within it one or more parshiyot (distinct Torah portions or sections).
-
E.
hasPageRangeInMushaf
Indicates that a text segment spans a specific range of pages within a particular mushaf (written copy of the Quran).
- F. None of above. chosen
Provenance (4 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.