Triple
T2113311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pikuach nefesh |
E42551
|
entity |
| Predicate | exceptionToOverride |
P28876
|
FINISHED |
| Object | idolatry |
—
|
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: idolatry | Statement: [pikuach nefesh, exceptionToOverride, idolatry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exceptionToOverride Context triple: [pikuach nefesh, exceptionToOverride, idolatry]
-
A.
exception
Indicates that a particular case does not follow the usual rule, pattern, or condition that applies to others.
-
B.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
C.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
-
D.
reasonForException
chosen
Indicates the specific cause or justification for why a normal rule, process, or condition does not apply in a given case.
-
E.
doesNotProvideExceptionFor
Indicates that one party or rule fails to grant an exemption, special case, or exclusion to another party or situation.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0495d0819097dc936540743b74 |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.