Triple
T34424422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiddushin |
E883629
|
entity |
| Predicate | timePeriodOfTalmudicDiscussion |
P302
|
FINISHED |
| Object | Amoraic era |
—
|
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: Amoraic era | Statement: [Kiddushin, timePeriodOfTalmudicDiscussion, Amoraic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfTalmudicDiscussion Context triple: [Kiddushin, timePeriodOfTalmudicDiscussion, Amoraic era]
-
A.
halakhicDebate
Indicates a formal religious-legal dispute or discussion over the correct interpretation or application of Jewish law between parties.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
roleInTalmud
Indicates that one entity holds a specific role, function, or status within the context of the Talmud.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
- 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_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 2 a.m.