Triple
T29655419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Templar Archives |
E750249
|
entity |
| Predicate | enablesUpgrade |
P117866
|
FINISHED |
| Object | Psionic Storm |
—
|
NE NERFINISHED |
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: Psionic Storm | Statement: [Templar Archives, enablesUpgrade, Psionic Storm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesUpgrade Context triple: [Templar Archives, enablesUpgrade, Psionic Storm]
-
A.
supportsUpgrade
chosen
Indicates that one entity is capable of accepting, enabling, or being compatible with an upgrade provided by another entity.
-
B.
upgradeFor
Indicates that one entity serves as an improved or enhanced replacement for another entity.
-
C.
upgradeable
Indicates that an entity can be improved or enhanced to a higher version, level, or capability.
-
D.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
E.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 6:54 p.m.