Triple
T37553328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orgrimmar Skyway |
E933638
|
entity |
| Predicate | verticalPosition |
P93627
|
FINISHED |
| Object | elevated above main city |
—
|
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: elevated above main city | Statement: [Orgrimmar Skyway, verticalPosition, elevated above main city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verticalPosition Context triple: [Orgrimmar Skyway, verticalPosition, elevated above main city]
-
A.
verticalLocation
chosen
Indicates a vertical positional relationship where one entity is located above or below another along the up-down axis.
-
B.
verticalBandPosition
Indicates the relative vertical placement or ordering of a band or stripe within a larger layout or structure.
-
C.
verticalOrder
Indicates that one entity is positioned directly above or below another along a vertical axis, establishing their relative vertical arrangement.
-
D.
verticalExtent
Indicates the total height or vertical span of an entity or region from its lowest to highest point.
-
E.
targetVertical
Indicates that one entity is directed toward, aligned with, or intended for a specific vertical market, domain, or industry segment.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.