Triple
T38593695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm Bow |
E932512
|
entity |
| Predicate | enablesAbilityEffect |
P165537
|
FINISHED |
| Object | reveals enemies with Sonic Arrow |
—
|
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: reveals enemies with Sonic Arrow | Statement: [Storm Bow, enablesAbilityEffect, reveals enemies with Sonic Arrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesAbilityEffect Context triple: [Storm Bow, enablesAbilityEffect, reveals enemies with Sonic Arrow]
-
A.
hasAbilityEffect
chosen
Indicates that one entity possesses or produces a specific ability-related effect on another entity or context.
-
B.
enabledAction
Indicates that a particular action is permitted, activated, or available to be performed in the given context.
-
C.
gainsAbility
Indicates that one entity comes to acquire or develop a new ability as a result of another entity or event.
-
D.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
E.
canEnable
Indicates that one entity has the capability or authority to activate, turn on, or make another entity or function operational.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.