Triple
T33464918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abel Magwitch |
E857018
|
entity |
| Predicate | learnsBeforeDeath |
P91711
|
FINISHED |
| Object | Pip's love and gratitude |
—
|
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: Pip's love and gratitude | Statement: [Abel Magwitch, learnsBeforeDeath, Pip's love and gratitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: learnsBeforeDeath Context triple: [Abel Magwitch, learnsBeforeDeath, Pip's love and gratitude]
-
A.
deathBefore
Indicates that one entity’s death occurred earlier in time than another entity’s death.
-
B.
deathPrecedes
Indicates that one entity’s death occurs earlier in time than another specified event or entity’s death.
-
C.
realizationBeforeDeath
chosen
Indicates that a significant understanding, insight, or fulfillment occurs prior to an entity’s death.
-
D.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
-
E.
earlyDeath
Indicates that an entity dies sooner than is typical or expected within a given context or population.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4f996948190a20e96059d5188cc |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.