Triple
T18283182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloister Wraiths |
E437913
|
entity |
| Predicate | haunt |
P15512
|
FINISHED |
| Object | secluded places |
—
|
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: secluded places | Statement: [Cloister Wraiths, haunt, secluded places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haunt Context triple: [Cloister Wraiths, haunt, secluded places]
-
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.
deathAttracting
Indicates a relationship where one entity’s death draws, lures, or otherwise causes another entity to come closer or be attracted.
-
C.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
D.
boggart
Indicates a transformative or illusory relationship where an entity manifests as, or is perceived in the form of, a boggart-like fear-inducing apparition.
-
E.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50057c5c881909fcda72f4a98c8c3 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.