Triple
T37553877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gehennas |
E933647
|
entity |
| Predicate | raidLockoutContext |
P188256
|
FINISHED |
| Object | weekly lockout in Classic WoW |
—
|
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 lockout in Classic WoW | Statement: [Gehennas, raidLockoutContext, weekly lockout in Classic WoW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidLockoutContext Context triple: [Gehennas, raidLockoutContext, weekly lockout in Classic WoW]
-
A.
raidLockout
chosen
Indicates that an entity is currently restricted from re-entering or re-participating in a raid instance for a specified lockout period.
-
B.
regionLocking
Indicates that access to or use of something is restricted based on the geographic region of the user or device.
-
C.
usesLockoutChip
Indicates that an entity employs a lockout chip mechanism to control or restrict access, operation, or compatibility.
-
D.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
-
E.
usesLockSystem
Indicates that one entity employs or relies on a locking mechanism or lock-based system provided by another entity.
- 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_69f76eca55bc8190acf25741793d5dac |
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. |
Created at: May 3, 2026, 4:17 p.m.