Triple
T37551129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Obsidian Sanctum |
E933591
|
entity |
| Predicate | supportsLockout |
P100154
|
FINISHED |
| Object | 10-player 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: 10-player lockout | Statement: [The Obsidian Sanctum, supportsLockout, 10-player lockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLockout Context triple: [The Obsidian Sanctum, supportsLockout, 10-player lockout]
-
A.
supportsLockoutType
chosen
Indicates that one entity is compatible with or able to operate using a specified lockout type.
-
B.
usesLockoutChip
Indicates that an entity employs a lockout chip mechanism to control or restrict access, operation, or compatibility.
-
C.
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.
-
D.
lockoutType
Indicates the specific category or reason for which access or operation has been restricted or locked out.
-
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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.