Triple
T37551217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onyxia's Lair (level 80 version) |
E933593
|
entity |
| Predicate | lootLevel |
P188183
|
FINISHED |
| Object | item level appropriate for level 80 |
—
|
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: item level appropriate for level 80 | Statement: [Onyxia's Lair (level 80 version), lootLevel, item level appropriate for level 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootLevel Context triple: [Onyxia's Lair (level 80 version), lootLevel, item level appropriate for level 80]
-
A.
lootItemLevelRange
chosen
Indicates the range of item levels that loot obtained from an entity, event, or container can fall within.
-
B.
LootType
Indicates the type or category of loot associated with an entity or event.
-
C.
lootPreference
Indicates a relationship where one entity has a favored choice or priority regarding the distribution or selection of loot.
-
D.
lootContext
Indicates the situational circumstances or environment in which the looting action occurs or is relevant.
-
E.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in a given context.
- 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.