Triple
T34424067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | סדר זרעים |
E883622
|
entity |
| Predicate | מסכת עם גמרא בבלית |
P95719
|
FINISHED |
| Object | ברכות |
—
|
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: ברכות | Statement: [סדר זרעים, מסכת עם גמרא בבלית, ברכות]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מסכת עם גמרא בבלית Context triple: [סדר זרעים, מסכת עם גמרא בבלית, ברכות]
-
A.
hasGemara
chosen
Indicates that an entity possesses, includes, or is associated with a Gemara (a Talmudic text or study component).
-
B.
appearsInTractate
Indicates that one entity (such as a topic, law, or passage) is contained within or discussed in a particular tractate.
-
C.
hasNoBavliGemaraForMostTractates
Indicates that there is no Babylonian Talmud (Bavli) Gemara text available for the majority of the tractates in question.
-
D.
שירת ב
Indicates that one entity served in or was on active duty within an organization, institution, or unit associated with the other entity.
-
E.
שירת בארגון קודם
Indicates that a person previously served in an organization.
- 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_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.