Triple
T1252340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kol Nidre |
E26904
|
entity |
| Predicate | doesNotAnnul |
P5512
|
FINISHED |
| Object | civil obligations |
—
|
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: civil obligations | Statement: [Kol Nidre, doesNotAnnul, civil obligations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotAnnul Context triple: [Kol Nidre, doesNotAnnul, civil obligations]
-
A.
doesNotAbolish
chosen
Indicates that one entity, action, or law does not eliminate, revoke, or put an end to another.
-
B.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
doesNotIssue
Indicates that one entity refrains from or fails to produce, grant, or distribute something (such as a document, order, or resource) to another entity.
-
D.
doesNotDetermine
Indicates that one entity or factor does not uniquely fix, decide, or specify the state, value, or outcome of another.
-
E.
doesNotProtect
Indicates that an entity fails to provide protection or safeguarding to another entity or object.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf875cf48190b6781d41097ee39b |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.