Triple
T29240116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albertine Simonet |
E741295
|
entity |
| Predicate | causesInNarrator |
P694
|
FINISHED |
| Object | intense jealousy |
—
|
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: intense jealousy | Statement: [Albertine Simonet, causesInNarrator, intense jealousy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causesInNarrator Context triple: [Albertine Simonet, causesInNarrator, intense jealousy]
-
A.
causeInStory
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
B.
hasCauseNarrative
Indicates that one entity provides a narrative or explanatory account of the cause or causal background of another entity or event.
-
C.
narratorIn
Indicates that one entity serves as the narrator or storytelling voice within the context of another entity (such as a work, scene, or narrative segment).
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
causeStatedByPerpetrators
Indicates that the stated cause or reason for an event or action is the one explicitly given by the perpetrators themselves.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 12:30 p.m.