Triple
T37553286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razor Hill Outskirts |
E933637
|
entity |
| Predicate | parentZone |
P2160
|
FINISHED |
| Object | Durotar |
—
|
NE NERFINISHED |
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: Durotar | Statement: [Razor Hill Outskirts, parentZone, Durotar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentZone Context triple: [Razor Hill Outskirts, parentZone, Durotar]
-
A.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
-
B.
parentRange
Indicates that one range is the direct parent or containing range of another range within a hierarchical structure.
-
C.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
D.
zone
chosen
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
E.
parentAct
Indicates that one entity performs an action in the role of a parent toward another entity, typically involving caregiving, guidance, or parental responsibility.
- 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_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:17 p.m.