Triple
T33996500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aliyah la-regel |
E871685
|
entity |
| Predicate | genderRequirementInBible |
P15554
|
FINISHED |
| Object | males obligated |
—
|
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: males obligated | Statement: [Aliyah la-regel, genderRequirementInBible, males obligated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderRequirementInBible Context triple: [Aliyah la-regel, genderRequirementInBible, males obligated]
-
A.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
B.
priesthoodGender
Indicates the gender associated with a particular priesthood role or office.
-
C.
genderOfMitzvah
Indicates the gender category associated with performing or being obligated in a particular mitzvah (commandment).
-
D.
biblicalStatus
Indicates that one entity has a particular standing, role, or classification within a biblical or scriptural context in relation to another entity.
-
E.
allowsOrdinationOfWomen
Indicates that an entity permits women to be formally ordained into official religious or clerical roles.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.