Triple
T37040836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Beyond Light |
E916775
|
entity |
| Predicate | addsNewExoticArmor |
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, addsNewExoticArmor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsNewExoticArmor Context triple: [Destiny 2: Beyond Light, addsNewExoticArmor, yes]
-
A.
addsNewGear
chosen
Indicates that an entity introduces or incorporates additional gear into an existing set, system, or configuration.
-
B.
designedArmor
Indicates that one entity created or planned the armor used or worn by another entity.
-
C.
armorVariant
Indicates that one armor is a specific version, type, or modification derived from another armor.
-
D.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
E.
armorGeneration
Indicates the creation or provision of protective armor for an entity, often as a result of some action, ability, or process.
- 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_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.