Triple
T6964955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Stranding 2: On the Beach |
E161463
|
entity |
| Predicate | hasCombat |
P73817
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Death Stranding 2: On the Beach, hasCombat, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombat Context triple: [Death Stranding 2: On the Beach, hasCombat, yes]
-
A.
usesCombatSystem
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
B.
sawCombat
Indicates that an entity directly participated in active military or armed conflict.
-
C.
introducedToCombat
Indicates that something was brought into use or implemented specifically for the purpose of addressing or mitigating a particular problem, threat, or undesirable condition.
-
D.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
E.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1049e0819097099a0e9d15f787 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d9bb57e88190a3a7cec34e3b617f |
completed | March 27, 2026, 7:25 p.m. |
Created at: March 27, 2026, 2:30 p.m.