Triple
T2113328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pikuach nefesh |
E42551
|
entity |
| Predicate | priorityOver |
P1616
|
FINISHED |
| Object | ritual observance |
—
|
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: ritual observance | Statement: [pikuach nefesh, priorityOver, ritual observance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priorityOver Context triple: [pikuach nefesh, priorityOver, ritual observance]
-
A.
missionPriority
Indicates the relative level of importance or urgency assigned to a mission compared to other missions or tasks.
-
B.
typeOfPriority
Indicates the specific priority level or category assigned to something relative to other items or tasks.
-
C.
upgradePriorityBasedOn
Indicates that the priority level of something is increased or adjusted according to the status, attributes, or importance of another specified factor or entity.
-
D.
confersPrecedenceIn
chosen
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
E.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
- 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.