Triple
T11642459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Nathria |
E276689
|
entity |
| Predicate | supportsLockoutType |
P100154
|
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: [Castle Nathria, supportsLockoutType, weekly raid lockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLockoutType Context triple: [Castle Nathria, supportsLockoutType, weekly raid lockout]
-
A.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
-
B.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
C.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
D.
canBeLocked
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
-
E.
supportsUserType
Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
- F. None of above. chosen
Provenance (4 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.