Triple
T37553780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackrock Depths |
E933645
|
entity |
| Predicate | hasLockout |
P100154
|
FINISHED |
| Object | standard 5-player instance lockout timer (original design) |
—
|
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: standard 5-player instance lockout timer (original design) | Statement: [Blackrock Depths, hasLockout, standard 5-player instance lockout timer (original design)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockout Context triple: [Blackrock Depths, hasLockout, standard 5-player instance lockout timer (original design)]
-
A.
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.
-
B.
supportsLockoutType
chosen
Indicates that one entity is compatible with or able to operate using a specified lockout type.
-
C.
usesLockoutChip
Indicates that an entity employs a lockout chip mechanism to control or restrict access, operation, or compatibility.
-
D.
hasLockNumber
Indicates that an entity is associated with a specific lock identified by a number.
-
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_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.