Triple
T35332712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madame de Merret |
E1020367
|
entity |
| Predicate | causeOfRemorse |
P191113
|
FINISHED |
| Object | complicity in the lover’s entombment |
—
|
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: complicity in the lover’s entombment | Statement: [Madame de Merret, causeOfRemorse, complicity in the lover’s entombment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfRemorse Context triple: [Madame de Merret, causeOfRemorse, complicity in the lover’s entombment]
-
A.
causeOfGuilt
chosen
Indicates that one entity is the reason or source of another entity’s feeling or state of guilt.
-
B.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
-
C.
causeOfDamnation
Indicates that one entity is the reason or source for another entity’s spiritual condemnation or eternal damnation.
-
D.
repentsFor
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
E.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:03 p.m.