Triple
T11746496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diablo Immortal |
E279292
|
entity |
| Predicate | playableMode |
P101127
|
FINISHED |
| Object | single-player |
—
|
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: single-player | Statement: [Diablo Immortal, playableMode, single-player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableMode Context triple: [Diablo Immortal, playableMode, single-player]
-
A.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
playType
Indicates the specific category or style of play or performance associated with an event or action.
-
C.
playbackOnly
Indicates that the relationship or action is limited to playing back existing content without allowing modification, recording, or other interactive operations.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
playableSide
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
- 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_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. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.