Triple
T37040835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Beyond Light |
E916775
|
entity |
| Predicate | addsNewExoticWeapons |
P186932
|
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: [Destiny 2: Beyond Light, addsNewExoticWeapons, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsNewExoticWeapons Context triple: [Destiny 2: Beyond Light, addsNewExoticWeapons, yes]
-
A.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
B.
addsNewGear
chosen
Indicates that an entity introduces or incorporates additional gear into an existing set, system, or configuration.
-
C.
enhancedArmament
Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
-
D.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
E.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
- F. None of above.
Provenance (3 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.