Triple
T33528033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Earnshaw |
E858694
|
entity |
| Predicate | decisionCauses |
P694
|
FINISHED |
| Object | family tensions between Hindley and Heathcliff |
—
|
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: family tensions between Hindley and Heathcliff | Statement: [Mr. Earnshaw, decisionCauses, family tensions between Hindley and Heathcliff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionCauses Context triple: [Mr. Earnshaw, decisionCauses, family tensions between Hindley and Heathcliff]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
C.
decisionBasis
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
D.
decisionEffect
Indicates that one decision leads to, influences, or determines a particular outcome or consequence.
-
E.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
- 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_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:39 a.m.