Triple
T37554425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydraxian Waterlords |
E933660
|
entity |
| Predicate | questHubZone |
P100057
|
FINISHED |
| Object | Azshara |
—
|
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: Azshara | Statement: [Hydraxian Waterlords, questHubZone, Azshara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questHubZone Context triple: [Hydraxian Waterlords, questHubZone, Azshara]
-
A.
questHubFor
Indicates a relationship where one entity serves as the central location or main coordination point for quests associated with another entity.
-
B.
zoneQuestHub
chosen
Indicates a relationship where a particular zone serves as the central hub or main base for quests within a game or system.
-
C.
questHubNPC
Indicates that an NPC serves as a central provider or coordinator of quests for players.
-
D.
otherZones
Indicates that an entity is associated with or belongs to zones that are distinct from a primary or reference zone.
-
E.
regionOfTour
Indicates that a specified geographic or administrative region is the location or scope within which a particular tour takes place.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.