Triple
T37551196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onyxia's Lair (level 80 version) |
E933593
|
entity |
| Predicate | designedForLevelCap |
P200293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Onyxia's Lair (level 80 version), designedForLevelCap, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForLevelCap Context triple: [Onyxia's Lair (level 80 version), designedForLevelCap, true]
-
A.
intendedPlayerLevel
Indicates the player level for which something (such as content, an item, or a challenge) is designed or meant to be used.
-
B.
raisedLevelCapFrom
Indicates that an entity has increased a previously existing maximum level limit from a specified lower value.
-
C.
raisesLevelCapTo
Indicates that one entity increases the maximum allowable level of another entity to a specified value.
-
D.
skillCeiling
Indicates the maximum level of proficiency or performance that can be achieved in a given skill, activity, or system.
-
E.
offeredAtLevel
Indicates that something is provided, presented, or made available at a specific level, tier, or stage.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
| PDg | Predicate description generation | batch_69ff7eb638c48190aeca7b85b9b698ab |
completed | May 9, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:17 p.m.