Triple
T5402018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead by Daylight |
E120798
|
entity |
| Predicate | survivorsPerMatch |
P63762
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Dead by Daylight, survivorsPerMatch, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsPerMatch Context triple: [Dead by Daylight, survivorsPerMatch, 4]
-
A.
numberOfSurvivingPlays
Indicates the count of plays by an author or in a collection that are still extant rather than lost.
-
B.
survivorsBuilt
Indicates that the entities identified as survivors constructed, created, or established the associated object or structure.
-
C.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
D.
survivorWith
Indicates a relationship where one entity survives an event or condition together with, or in the presence of, another entity.
-
E.
survivorTerm
Indicates that one entity is designated as the surviving or remaining party in relation to another entity, often after a loss, termination, or adverse event.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd8931302c81908afcb0f011e91f09 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:04 p.m.