Triple
T34424647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horayot |
E883634
|
entity |
| Predicate | hasBabylonianTalmudPages |
P98050
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Horayot, hasBabylonianTalmudPages, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBabylonianTalmudPages Context triple: [Horayot, hasBabylonianTalmudPages, 14]
-
A.
hasBabylonianTalmudPagesApprox
chosen
Indicates an approximate number of pages attributed to an entity in the Babylonian Talmud.
-
B.
hasGemara
Indicates that an entity possesses, includes, or is associated with a Gemara (a Talmudic text or study component).
-
C.
hasJerusalemTalmud
Indicates that an entity possesses, is associated with, or is characterized by the Jerusalem Talmud.
-
D.
hasJerusalemTalmudChapters
Indicates that an entity (such as a tractate or section) is associated with a specified number or set of chapters in the Jerusalem Talmud.
-
E.
hasNoBavliGemaraForMostTractates
Indicates that there is no Babylonian Talmud (Bavli) Gemara text available for the majority of the tractates in question.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 2 a.m.