Triple
T5111248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shrieking Shack |
E115217
|
entity |
| Predicate | actuallyUsedFor |
P98
|
FINISHED |
| Object | safe transformation place for a werewolf |
—
|
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: safe transformation place for a werewolf | Statement: [The Shrieking Shack, actuallyUsedFor, safe transformation place for a werewolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuallyUsedFor Context triple: [The Shrieking Shack, actuallyUsedFor, safe transformation place for a werewolf]
-
A.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for 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.