Triple
T37923298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs Ramsay |
E946021
|
entity |
| Predicate | deathStatusInNarrative |
P190413
|
FINISHED |
| Object | dies between The Window and Time Passes |
—
|
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: dies between The Window and Time Passes | Statement: [Mrs Ramsay, deathStatusInNarrative, dies between The Window and Time Passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathStatusInNarrative Context triple: [Mrs Ramsay, deathStatusInNarrative, dies between The Window and Time Passes]
-
A.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
B.
deathNarrativeFunction
Indicates that a character’s death serves a specific narrative role or function within the story’s structure or themes.
-
C.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
D.
deathOccurred
chosen
Indicates that a death event has taken place involving the specified entity or entities.
-
E.
deathInterpretedAs
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:20 p.m.