Triple
T37457456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagger Mastery |
E930834
|
entity |
| Predicate | replacesHeroPowerOf |
P197377
|
FINISHED |
| Object | Rogue heroes |
—
|
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: Rogue heroes | Statement: [Dagger Mastery, replacesHeroPowerOf, Rogue heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesHeroPowerOf Context triple: [Dagger Mastery, replacesHeroPowerOf, Rogue heroes]
-
A.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
B.
replacesPowerUp
Indicates that one power-up is substituted for or takes the place of another in a given context or state.
-
C.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
D.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
E.
invokesPower
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
| PDg | Predicate description generation | batch_69fe8dde8d008190b03dc0f97618073c |
completed | May 9, 2026, 1:29 a.m. |
Created at: May 3, 2026, 4:17 p.m.