Triple
T5402034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead by Daylight |
E120798
|
entity |
| Predicate | objectiveForKiller |
P56726
|
FINISHED |
| Object | sacrifice survivors to The Entity |
—
|
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: sacrifice survivors to The Entity | Statement: [Dead by Daylight, objectiveForKiller, sacrifice survivors to The Entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveForKiller Context triple: [Dead by Daylight, objectiveForKiller, sacrifice survivors to The Entity]
-
A.
actorObjective
chosen
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
-
B.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
C.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
-
D.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
E.
targetOfCrime
Indicates that the subject is the person, organization, or entity against whom the referenced crime is committed.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.