Triple
T38643321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vashj'ir |
E938656
|
entity |
| Predicate | startingQuestHubAlliance |
P183546
|
FINISHED |
| Object | Stormwind City |
—
|
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: Stormwind City | Statement: [Vashj'ir, startingQuestHubAlliance, Stormwind City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingQuestHubAlliance Context triple: [Vashj'ir, startingQuestHubAlliance, Stormwind City]
-
A.
introducedQuestHub
Indicates that an entity has presented or made a quest hub available to another entity or group.
-
B.
hasQuestHubIn
chosen
Indicates that a quest hub is located within or associated with a particular place or region.
-
C.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
D.
allianceHubFor
Indicates that one entity serves as a central coordinating hub or focal point for an alliance involving another entity.
-
E.
questProgression
Indicates the ordered advancement of a quest through its defined stages or milestones.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0189f3f0248190a1b018164d18e6f5 |
completed | May 11, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0187ee0920819097047bb55e1f9506 |
completed | May 11, 2026, 7:40 a.m. |
Created at: May 3, 2026, 4:32 p.m.