Triple
T5402125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond (Dead by Daylight perk) |
E120800
|
entity |
| Predicate | stacking |
P63770
|
FINISHED |
| Object | does not stack with itself |
—
|
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: does not stack with itself | Statement: [Bond (Dead by Daylight perk), stacking, does not stack with itself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stacking Context triple: [Bond (Dead by Daylight perk), stacking, does not stack with itself]
-
A.
stackingConfiguration
Indicates how multiple entities are arranged or layered on top of each other in a specific order or configuration.
-
B.
numberOfStacks
Indicates the count of distinct stacks associated with or contained within a given entity.
-
C.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
D.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
E.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
- 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.