Triple
T37897189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogu'shan Palace |
E945311
|
entity |
| Predicate | lootLevelOriginalHeroic |
P189592
|
FINISHED |
| Object | 463 |
—
|
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: 463 | Statement: [Mogu'shan Palace, lootLevelOriginalHeroic, 463]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootLevelOriginalHeroic Context triple: [Mogu'shan Palace, lootLevelOriginalHeroic, 463]
-
A.
heroicLevel
Indicates the degree or extent to which an entity exhibits heroism or heroic qualities.
-
B.
lootValue
Indicates the total worth or value assigned to items obtained as loot in a given context or event.
-
C.
lootItemLevelRange
Indicates the range of item levels that loot obtained from an entity, event, or container can fall within.
-
D.
heroicLockout
Indicates a situation where an entity is prevented or restricted from accessing heroic-level content, activities, or opportunities, typically due to prior participation or imposed limits.
-
E.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in a given context.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.