Triple
T30596784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seal of the Vishanti |
E778808
|
entity |
| Predicate | canCounteract |
P158943
|
FINISHED |
| Object | demonic entities |
—
|
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: demonic entities | Statement: [Seal of the Vishanti, canCounteract, demonic entities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCounteract Context triple: [Seal of the Vishanti, canCounteract, demonic entities]
-
A.
opposesEffectOf
Indicates that one entity counteracts, reduces, or nullifies the effect produced by another entity.
-
B.
counterplay
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
C.
counterMeasureAgainst
Indicates a relationship where one entity serves as a response or defensive action intended to prevent, mitigate, or neutralize the effects of another entity.
-
D.
canOppose
chosen
Indicates that one entity has the ability or capacity to resist, counteract, or act in opposition to another entity or its actions.
-
E.
primaryAdversaryCapabilityCountered
Indicates that a primary adversary capability is neutralized, mitigated, or otherwise rendered ineffective by a specified countermeasure or action.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6897fc2e881909e2bd183eb7fddc9 |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:24 p.m.