Triple
T37503772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlemode |
E932038
|
entity |
| Predicate | featuresPlayableSide |
P100341
|
FINISHED |
| Object | Slayer |
E131441
|
NE 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: Slayer | Statement: [Battlemode, featuresPlayableSide, Slayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPlayableSide Context triple: [Battlemode, featuresPlayableSide, Slayer]
-
A.
playableSide
chosen
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
-
B.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
C.
featuresPlayableFaction
Indicates that a game or scenario includes a faction that players can actively control or play as.
-
D.
gameFeatures
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
E.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
- F. None of above.
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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409efb44b0819085eb18ac4ae3ad16 |
completed | June 28, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.