Triple
T23954413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindley Earnshaw |
E603742
|
entity |
| Predicate | isJealousOf |
P141339
|
FINISHED |
| Object | Heathcliff |
—
|
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: Heathcliff | Statement: [Hindley Earnshaw, isJealousOf, Heathcliff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJealousOf Context triple: [Hindley Earnshaw, isJealousOf, Heathcliff]
-
A.
isEnviedBy
chosen
Indicates that one entity is the object of another entity’s envy or jealousy.
-
B.
isEmbittered
Indicates that an entity harbors persistent bitterness or resentment, typically as a result of past experiences or perceived wrongs.
-
C.
isSympatheticTo
Indicates that one entity feels or expresses compassion, understanding, or emotional support toward another entity.
-
D.
hasJealousHusbandCharacter
Indicates that an entity includes or involves a husband character who experiences or expresses jealousy in the context of the relationship or narrative.
-
E.
isGaslitBy
Indicates that one entity is being psychologically manipulated by another to make them doubt their own perceptions, memories, or sanity.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d616ec81908c796894f40f3015 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.