Triple
T33528047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Earnshaw |
E858694
|
entity |
| Predicate | causesJealousyIn |
P141339
|
FINISHED |
| Object | Hindley Earnshaw |
—
|
NE NERFINISHED |
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: Hindley Earnshaw | Statement: [Mr. Earnshaw, causesJealousyIn, Hindley Earnshaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causesJealousyIn Context triple: [Mr. Earnshaw, causesJealousyIn, Hindley Earnshaw]
-
A.
causeOfBetrayal
Indicates that one entity is the reason or motivating factor behind another entity’s act of betrayal.
-
B.
isEnviedBy
chosen
Indicates that one entity is the object of another entity’s envy or jealousy.
-
C.
hasJealousHusbandCharacter
Indicates that an entity includes or involves a husband character who experiences or expresses jealousy in the context of the relationship or narrative.
-
D.
causeOfVengeance
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 1:39 a.m.