Triple
T36374715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moed Katan |
E895866
|
entity |
| Predicate | traditionAttributesGemaraTo |
P13958
|
FINISHED |
| Object | Amoraim |
—
|
NE NERFINISHED |
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: Amoraim | Statement: [Moed Katan, traditionAttributesGemaraTo, Amoraim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionAttributesGemaraTo Context triple: [Moed Katan, traditionAttributesGemaraTo, Amoraim]
-
A.
rabbinicTradition
Indicates that something is part of, derived from, or in accordance with the teachings, interpretations, or practices of rabbinic Jewish tradition.
-
B.
hasGemara
Indicates that an entity possesses, includes, or is associated with a Gemara (a Talmudic text or study component).
-
C.
mentionedInTraditionOf
Indicates that something is referenced, recognized, or discussed within the body of beliefs, practices, or narratives of a particular tradition.
-
D.
traditionAscribes
chosen
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
textBelongsToTradition
Indicates that a given text is associated with, derived from, or recognized as part of a particular intellectual, cultural, or religious tradition.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.