Triple
T1207964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javert |
E25931
|
entity |
| Predicate | reasonForSuicide |
P144
|
FINISHED |
| Object | inability to reconcile law with mercy |
—
|
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: inability to reconcile law with mercy | Statement: [Javert, reasonForSuicide, inability to reconcile law with mercy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSuicide Context triple: [Javert, reasonForSuicide, inability to reconcile law with mercy]
-
A.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
B.
reasonForTribute
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
-
C.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
E.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.