Triple
T38645572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menagerie of the Master |
E938704
|
entity |
| Predicate | lootLockoutType |
P188258
|
FINISHED |
| Object | weekly 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 lockout | Statement: [Menagerie of the Master, lootLockoutType, weekly lockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootLockoutType Context triple: [Menagerie of the Master, lootLockoutType, weekly lockout]
-
A.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in a given context.
-
B.
LootType
Indicates the type or category of loot associated with an entity or event.
-
C.
lockoutType
chosen
Indicates the specific category or reason for which access or operation has been restricted or locked out.
-
D.
lootPreference
Indicates a relationship where one entity has a favored choice or priority regarding the distribution or selection of loot.
-
E.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.