Triple
T13243320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renewal Judaism |
E315333
|
entity |
| Predicate | hasApproachToHalakha |
P8264
|
FINISHED |
| Object | flexible |
—
|
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: flexible | Statement: [Renewal Judaism, hasApproachToHalakha, flexible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachToHalakha Context triple: [Renewal Judaism, hasApproachToHalakha, flexible]
-
A.
halakhicApproach
Indicates an entity’s method, stance, or interpretive framework for applying or understanding Jewish law (halakha) in practice.
-
B.
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.
-
C.
halakhicStatus
Indicates the formal standing or classification of an entity according to Jewish law (halakha), especially in terms of what is religiously permitted, required, or prohibited.
-
D.
viewsHalakhaAs
chosen
Indicates that one entity regards or interprets Halakha (Jewish law) in a particular way, such as considering it authoritative, binding, flexible, or symbolic.
-
E.
precedenceInHalakha
Indicates that, according to Halakha (Jewish law), one entity or rule takes priority over another in cases of conflict or ordering.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5b06148190a44e698bbe5cd529 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:23 p.m.