Triple
T16866499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackmoor |
E410052
|
entity |
| Predicate | settingForEvents |
P6628
|
FINISHED |
| Object | murders in The Wolfman (2010 film) |
—
|
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: murders in The Wolfman (2010 film) | Statement: [Blackmoor, settingForEvents, murders in The Wolfman (2010 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingForEvents Context triple: [Blackmoor, settingForEvents, murders in The Wolfman (2010 film)]
-
A.
settingOfActivities
Indicates that a particular place or context serves as the environment in which certain activities occur or are carried out.
-
B.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
C.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
D.
featuresEvent
chosen
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
E.
setAgainstEvent
Indicates that one event is positioned or framed in opposition or contrast to another event.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b5088f208190abfe937633ebe3fe |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.