Triple
T37874395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warbands (Diablo Immortal) |
E944680
|
entity |
| Predicate | gameModeScope |
P100844
|
FINISHED |
| Object | PvE only |
—
|
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: PvE only | Statement: [Warbands (Diablo Immortal), gameModeScope, PvE only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameModeScope Context triple: [Warbands (Diablo Immortal), gameModeScope, PvE only]
-
A.
gameModeRule
Indicates a rule or constraint that defines how a particular game mode operates or is played.
-
B.
gameModeRelevance
chosen
Indicates how strongly or in what way something is related or applicable to a particular game mode.
-
C.
gameModeStatus
Indicates the current state or condition of a game mode, such as whether it is active, available, or in a particular operational phase.
-
D.
gameModeDesign
Indicates that one entity defines or specifies the rules, structure, or configuration of a particular game mode for another entity.
-
E.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game mode.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:19 p.m.