Triple
T5402130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond (Dead by Daylight perk) |
E120800
|
entity |
| Predicate | targetPlayerType |
P61189
|
FINISHED |
| Object | cooperative players |
—
|
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: cooperative players | Statement: [Bond (Dead by Daylight perk), targetPlayerType, cooperative players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPlayerType Context triple: [Bond (Dead by Daylight perk), targetPlayerType, cooperative players]
-
A.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
targetOffenderType
Indicates the specific category or type of offender that an action, rule, or condition is directed toward.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
E.
intendedPlayers
chosen
Indicates the players for whom something (such as a game, item, or activity) is designed or meant to be used.
- 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.