Triple
T37705090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dazar'alor |
E939176
|
entity |
| Predicate | inGameRoleForHorde |
P190122
|
FINISHED |
| Object | main capital in Battle for Azeroth |
—
|
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: main capital in Battle for Azeroth | Statement: [Dazar'alor, inGameRoleForHorde, main capital in Battle for Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inGameRoleForHorde Context triple: [Dazar'alor, inGameRoleForHorde, main capital in Battle for Azeroth]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
gameRoleInHotS
Indicates the specific role or function an entity has within the game Heroes of the Storm (HotS), such as its position or responsibility in gameplay.
-
C.
gameRoleInHearthstone
Indicates that an entity has a specific role or function within the game Hearthstone.
-
D.
gameRoleForPlayers
Indicates the specific role or function that players have within a particular game or gameplay context.
-
E.
roleAtRagnarok
Indicates the specific function, position, or part an entity is expected to have or perform during Ragnarok.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.