Triple
T38644478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rise of Azshara |
E938680
|
entity |
| Predicate | introducesZone |
P199613
|
FINISHED |
| Object | Nazjatar |
—
|
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: Nazjatar | Statement: [Rise of Azshara, introducesZone, Nazjatar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesZone Context triple: [Rise of Azshara, introducesZone, Nazjatar]
-
A.
introducedAsSingleZone
Indicates that something is presented or defined as a single, unified zone rather than being divided into multiple zones.
-
B.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
C.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
D.
otherZones
Indicates that an entity is associated with or belongs to zones that are distinct from a primary or reference zone.
-
E.
exampleZoneName
Indicates that an entity is associated with a zone identified by a specific example or placeholder name.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: May 3, 2026, 4:32 p.m.