Triple
T10736465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seder Nashim |
E253206
|
entity |
| Predicate | religiousLawCodeFor |
P17762
|
FINISHED |
| Object | Jewish families |
—
|
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: Jewish families | Statement: [Seder Nashim, religiousLawCodeFor, Jewish families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousLawCodeFor Context triple: [Seder Nashim, religiousLawCodeFor, Jewish families]
-
A.
scripturalLawCode
Indicates that one entity is a law code or set of legal prescriptions as defined or authorized by a particular scriptural or religious text for another entity.
-
B.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
C.
halachicSection
Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
-
D.
religiousCanon
Indicates that something is formally recognized as part of an established body of authoritative religious texts or doctrine.
-
E.
halakhicSource
chosen
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71022aee0819091a5790d3dee6777 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.