Triple
T37040833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny 2: Beyond Light |
E916775
|
entity |
| Predicate | addsPowerCapIncrease |
P99611
|
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, addsPowerCapIncrease, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsPowerCapIncrease Context triple: [Destiny 2: Beyond Light, addsPowerCapIncrease, yes]
-
A.
increasedISSPowerCapacity
Indicates that an entity has caused or experienced an increase in the International Space Station’s power generation or supply capacity.
-
B.
raisedLevelCapFrom
chosen
Indicates that an entity has increased a previously existing maximum level limit from a specified lower value.
-
C.
canBePoweredUp
Indicates that an entity has the capability to receive additional power or energy, enhancing its state or functionality.
-
D.
gainedPowerAfter
Indicates that one entity acquired power, authority, or influence subsequent to an event, condition, or action involving another entity.
-
E.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
- 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_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.