Triple
T38583333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zandalari trolls |
E932291
|
entity |
| Predicate | zoneRoleInGame |
P88332
|
FINISHED |
| Object | Horde leveling continent 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: Horde leveling continent in Battle for Azeroth | Statement: [Zandalari trolls, zoneRoleInGame, Horde leveling continent in Battle for Azeroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneRoleInGame Context triple: [Zandalari trolls, zoneRoleInGame, Horde leveling continent in Battle for Azeroth]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
zoneNumberInGame
Indicates that an entity is associated with a specific numbered zone within a game.
-
C.
zoningRole
Indicates the specific function, restriction, or regulatory status assigned to a property or area under zoning regulations.
-
D.
regionInGame
chosen
Indicates that a specific region or area exists within or is part of a particular game.
-
E.
gameRoleForPlayers
Indicates the specific role or function that players have within a particular game or gameplay context.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.