Triple
T37874304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demon Hunter |
E944678
|
entity |
| Predicate | availableInGame |
P88329
|
FINISHED |
| Object | Diablo Immortal |
—
|
NE NERFINISHED |
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: Diablo Immortal | Statement: [Demon Hunter, availableInGame, Diablo Immortal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableInGame Context triple: [Demon Hunter, availableInGame, Diablo Immortal]
-
A.
playableInGame
chosen
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game mode.
-
C.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
D.
playsInGame
Indicates that an entity participates as a player in a particular game or match.
-
E.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
- 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:19 p.m.