Triple
T37471504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spires of Ascension |
E931163
|
entity |
| Predicate | supportsKeystoneAffixes |
P205914
|
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: [Spires of Ascension, supportsKeystoneAffixes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeystoneAffixes Context triple: [Spires of Ascension, supportsKeystoneAffixes, yes]
-
A.
hasMythicPlusAffixSynergy
Indicates that two or more Mythic Plus affixes interact in a way that meaningfully alters or enhances their combined gameplay impact.
-
B.
canBeEnchantedWith
Indicates that an entity is capable of receiving or being affected by a specified enchantment.
-
C.
canBeSocketed
Indicates that one entity is capable of being inserted into or mounted within another as a compatible socketed component.
-
D.
isLegendaryForSet
Indicates that an entity is classified as a legendary item specifically within the context of a given set or collection.
-
E.
hasSoulGemAbility
Indicates that an entity possesses the capability to use, interact with, or be affected by a soul gem and its associated powers or functions.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.