Triple
T37012515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Shotgun |
E915986
|
entity |
| Predicate | hasMasteryUpgrade |
P5357
|
FINISHED |
| Object | Explosive Shot mastery |
—
|
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: Explosive Shot mastery | Statement: [Combat Shotgun, hasMasteryUpgrade, Explosive Shot mastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMasteryUpgrade Context triple: [Combat Shotgun, hasMasteryUpgrade, Explosive Shot mastery]
-
A.
hasUpgradeLevel
Indicates that an entity possesses a specific upgrade stage or level within a progression or enhancement system.
-
B.
isMasterOf
Indicates that one entity holds a position of control, authority, or ownership over another entity.
-
C.
hasUpgrade
chosen
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
D.
expansionsIncreasedMasteriesTo
Indicates that expansions caused an increase in the number or level of masteries for the target entity.
-
E.
hasSwordmaster
Indicates that an entity is associated with or possesses a designated swordmaster, typically as a mentor, trainer, or specialist in swordsmanship.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a035ead9ee0819099806d2670dc9c50 |
completed | May 12, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_6a035dc9210c8190a9044c6a53211520 |
completed | May 12, 2026, 5:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.