Triple
T5401998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead by Daylight |
E120798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | asymmetric multiplayer game |
C10370
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: asymmetric multiplayer game Context triple: [Dead by Daylight, instanceOf, asymmetric multiplayer game]
-
A.
multiplayer game
chosen
A multiplayer game is an interactive digital or physical game in which two or more players participate simultaneously or asynchronously, often collaborating or competing within a shared set of rules and objectives.
-
B.
dynamic game
A dynamic game is a strategic interaction among multiple decision-makers that unfolds over time, where players’ choices at each stage can depend on past actions and information, influencing future payoffs and outcomes.
-
C.
mathematical game
A mathematical game is a structured activity or problem governed by explicit rules in which players make decisions or moves, often analyzed using mathematical concepts such as strategy, probability, and optimization.
-
D.
combinatorial game
A combinatorial game is a two-player, perfect-information game with no chance elements where players move alternately and the outcome depends solely on their strategic choices under well-defined rules.
-
E.
zero-player game
A zero-player game is a simulation or system that evolves automatically from its initial state without any ongoing input or decisions from human or computer-controlled players.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 20, 2026, 2:04 p.m.