Triple
T28248778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean Calas |
E712258
|
entity |
| Predicate | posthumouslyClearedOf |
P112223
|
FINISHED |
| Object | murder of his son |
—
|
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: murder of his son | Statement: [Jean Calas, posthumouslyClearedOf, murder of his son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumouslyClearedOf Context triple: [Jean Calas, posthumouslyClearedOf, murder of his son]
-
A.
clearedOf
Indicates that an entity has been officially found not responsible for, or freed from suspicion of, a previously alleged wrongdoing, charge, or negative condition.
-
B.
cleared
Indicates that an entity has removed obstacles, doubts, or restrictions from another entity or from a particular state or situation.
-
C.
isClearedBy
Indicates that one entity removes an obstruction, restriction, or pending status from another entity, allowing it to proceed or be considered resolved.
-
D.
posthumousAction
chosen
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
-
E.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 11:03 p.m.