Triple
T36958768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hacx: Twitch 'n Kill |
E914254
|
entity |
| Predicate | hasGameContent |
P187452
|
FINISHED |
| Object | custom graphics |
—
|
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: custom graphics | Statement: [Hacx: Twitch 'n Kill, hasGameContent, custom graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameContent Context triple: [Hacx: Twitch 'n Kill, hasGameContent, custom graphics]
-
A.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
B.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
C.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
D.
hasGameTitle
Indicates that an entity is associated with or identified by a specific game title.
-
E.
hasGameTag
Indicates that a game is associated with a particular descriptive tag or category label.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:13 p.m.