Triple
T37515057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duelist |
E932612
|
entity |
| Predicate | canUseSkillGems |
P188698
|
FINISHED |
| Object | attack skill gems |
—
|
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: attack skill gems | Statement: [Duelist, canUseSkillGems, attack skill gems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseSkillGems Context triple: [Duelist, canUseSkillGems, attack skill gems]
-
A.
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.
-
B.
canUseHero
Indicates that an entity is permitted or able to use a specified hero character.
-
C.
hasSkillTree
Indicates that an entity is associated with a structured progression of skills or abilities, typically organized in a branching or hierarchical form.
-
D.
hasJewel
Indicates that one entity possesses, contains, or is adorned with a jewel in relation to another entity.
-
E.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.