Triple
T8156986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathy Earnshaw |
E190473
|
entity |
| Predicate | hasGhostlyPresence |
P15512
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cathy Earnshaw, hasGhostlyPresence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGhostlyPresence Context triple: [Cathy Earnshaw, hasGhostlyPresence, true]
-
A.
hasGhostCharacter
Indicates that an entity includes, features, or is associated with a character that is a ghost.
-
B.
hasSupernaturalPerceptionOf
Indicates that one entity possesses a supernatural or extrasensory awareness, insight, or perception specifically directed toward another entity.
-
C.
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.
-
D.
containsSupernaturalElement
Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
-
E.
hasPerspectiveOnParanormal
Indicates that one entity holds a particular view, belief, or attitude regarding paranormal phenomena in relation to another entity or topic.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d8a37481909397b5cc321b94be |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.