Triple
T6422396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaddish |
E127974
|
entity |
| Predicate | doesNotMention |
P57963
|
FINISHED |
| Object | death |
—
|
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: death | Statement: [Kaddish, doesNotMention, death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotMention Context triple: [Kaddish, doesNotMention, death]
-
A.
doesNotSpecify
Indicates that the subject intentionally leaves some information, detail, or attribute undefined or unspecified with respect to the object.
-
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.
notAbout
chosen
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
D.
doesNotConsider
Indicates that one entity fails or chooses not to take another entity or factor into account when forming judgments, decisions, or actions.
-
E.
doesNotImply
Indicates that the truth of one statement or condition does not guarantee or lead to the truth of another statement or condition.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690576c48190b5db5464eacc9de3 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.