Triple
T5111247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shrieking Shack |
E115217
|
entity |
| Predicate | rumoredToBe |
P30422
|
FINISHED |
| Object | haunted |
—
|
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: haunted | Statement: [The Shrieking Shack, rumoredToBe, haunted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rumoredToBe Context triple: [The Shrieking Shack, rumoredToBe, haunted]
-
A.
rumoredTarget
Indicates that an entity is believed or speculated, based on rumor or unconfirmed information, to be the intended target of another entity or action.
-
B.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
C.
hasBeenSpeculatedToBe
chosen
Indicates that something has been suggested or hypothesized, without firm evidence, to possibly be or correspond to something else.
-
D.
hasSequelRumors
Indicates that there are rumors or unconfirmed reports suggesting a sequel exists or may be produced for the referenced work.
-
E.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ad362c8190b9cbded390aaea3c |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.