Triple
T11746502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diablo Immortal |
E279292
|
entity |
| Predicate | primaryGameplay |
P39812
|
FINISHED |
| Object | dungeon crawling |
—
|
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: dungeon crawling | Statement: [Diablo Immortal, primaryGameplay, dungeon crawling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGameplay Context triple: [Diablo Immortal, primaryGameplay, dungeon crawling]
-
A.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
B.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
C.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
D.
gameFeatures
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
E.
games
Indicates that one entity participates in, is associated with, or is characterized by playing or engaging in games with another entity.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50763a081908597da118bd0a64e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.