Triple
T37554450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydraxian Waterlords |
E933660
|
entity |
| Predicate | primaryActivityForPlayers |
P100832
|
FINISHED |
| Object | raiding Molten Core |
—
|
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: raiding Molten Core | Statement: [Hydraxian Waterlords, primaryActivityForPlayers, raiding Molten Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryActivityForPlayers Context triple: [Hydraxian Waterlords, primaryActivityForPlayers, raiding Molten Core]
-
A.
primaryGame
Indicates that one game is the main or most significant game associated with an entity (such as a person, team, or event) among possibly several games.
-
B.
primaryUseByPlayers
chosen
Indicates the main way in which players typically use or interact with the referenced entity.
-
C.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
D.
playerActivities
Indicates the various actions, events, or engagements that a player participates in within a given context or system.
-
E.
primaryPlayerGroup
Indicates the group that serves as the main or principal set of players associated with a given context or activity.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.