Triple
T37897159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogu'shan Palace |
E945311
|
entity |
| Predicate | entranceZoneLevelRange |
P190427
|
FINISHED |
| Object | 90 |
—
|
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: 90 | Statement: [Mogu'shan Palace, entranceZoneLevelRange, 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceZoneLevelRange Context triple: [Mogu'shan Palace, entranceZoneLevelRange, 90]
-
A.
zoneLevelRange
Indicates the range of zone levels within which a given condition, rule, or classification applies.
-
B.
hasEntranceElevation
Indicates the elevation at which an entity’s entrance is located, typically measured relative to a reference level such as sea level or ground level.
-
C.
zoneLevelRangeAtLaunch
Indicates the range of zone levels that apply at the moment something is launched or begins.
-
D.
entranceHeight
Indicates the vertical measurement of how tall an entrance is.
-
E.
combatLevelRange
Indicates the range of combat levels within which two entities can validly or effectively engage in combat with each other.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:19 p.m.