Triple
T34424392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiddushin |
E883629
|
entity |
| Predicate | openingMishnahTopic |
P122117
|
FINISHED |
| Object | ways a woman is betrothed |
—
|
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: ways a woman is betrothed | Statement: [Kiddushin, openingMishnahTopic, ways a woman is betrothed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMishnahTopic Context triple: [Kiddushin, openingMishnahTopic, ways a woman is betrothed]
-
A.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
-
B.
appearsInTractate
chosen
Indicates that one entity (such as a topic, law, or passage) is contained within or discussed in a particular tractate.
-
C.
positionInMishnahOrders
Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
-
D.
halachicTopic
Indicates that something is related to, concerns, or falls under a particular topic within Jewish law (halacha).
-
E.
openingWordsHebrew
Indicates that the specified words are the opening (initial) words of a text or passage in Hebrew.
- 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_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 2 a.m.