Triple
T5402129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond (Dead by Daylight perk) |
E120800
|
entity |
| Predicate | loadoutSlot |
P63771
|
FINISHED |
| Object | perk slot |
—
|
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: perk slot | Statement: [Bond (Dead by Daylight perk), loadoutSlot, perk slot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadoutSlot Context triple: [Bond (Dead by Daylight perk), loadoutSlot, perk slot]
-
A.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
B.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
-
C.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
D.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
-
E.
internalWeaponsBays
Indicates that an entity is equipped with weapons storage or launch systems housed within its internal structure rather than mounted externally.
- 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.