Triple
T3282888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sethe |
E68912
|
entity |
| Predicate | hauntedBy |
P15512
|
FINISHED |
| Object | ghost of her dead daughter |
—
|
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: ghost of her dead daughter | Statement: [Sethe, hauntedBy, ghost of her dead daughter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hauntedBy Context triple: [Sethe, hauntedBy, ghost of her dead daughter]
-
A.
haunts
chosen
Indicates that one entity persistently appears in, lingers around, or psychologically troubles another entity or place, often in a recurring or unsettling way.
-
B.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
-
C.
associatedSpirit
Indicates a relationship where one entity is linked to or accompanied by a particular spirit, often as a guide, protector, or defining supernatural presence.
-
D.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
E.
hungFrom
Indicates that one entity is suspended and supported by another entity from above.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0345d448190a1f936abe7748e33 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.