Triple
T37872604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogu'shan Vaults |
E944641
|
entity |
| Predicate | hasLockoutType |
P188258
|
FINISHED |
| Object | weekly raid lockout |
—
|
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: weekly raid lockout | Statement: [Mogu'shan Vaults, hasLockoutType, weekly raid lockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockoutType Context triple: [Mogu'shan Vaults, hasLockoutType, weekly raid lockout]
-
A.
supportsLockoutType
Indicates that one entity is compatible with or able to operate using a specified lockout type.
-
B.
hasSharedLockoutWith
Indicates that two or more entities are configured to enter or be controlled by the same lockout mechanism, so that restricting access or operation for one also restricts it for the others.
-
C.
hasLockType
Indicates that an entity is associated with or uses a specific type or category of lock.
-
D.
lockoutType
chosen
Indicates the specific category or reason for which access or operation has been restricted or locked out.
-
E.
usesLockoutChip
Indicates that an entity employs a lockout chip mechanism to control or restrict access, operation, or compatibility.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.