Triple
T37555228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleak Redoubt |
E933679
|
entity |
| Predicate | combatLevelRange |
P189159
|
FINISHED |
| Object | Shadowlands-level characters |
—
|
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: Shadowlands-level characters | Statement: [Bleak Redoubt, combatLevelRange, Shadowlands-level characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatLevelRange Context triple: [Bleak Redoubt, combatLevelRange, Shadowlands-level characters]
-
A.
gearItemLevelRange
Indicates the range of item levels that a piece of gear can or does fall within.
-
B.
difficultyClassRange
Indicates the range of difficulty classes within which an action, task, or challenge is considered to fall.
-
C.
yLevelRange
Indicates that one entity’s vertical position or height falls within a specified range relative to another entity or reference level.
-
D.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
E.
lootItemLevelRange
Indicates the range of item levels that loot obtained from an entity, event, or container can fall within.
- 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_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:17 p.m.