Triple
T37204340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT: Evilution |
E922125
|
entity |
| Predicate | hasDeathmatchMode |
P200509
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TNT: Evilution, hasDeathmatchMode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeathmatchMode Context triple: [TNT: Evilution, hasDeathmatchMode, true]
-
A.
gameModeStatus
Indicates the current state or condition of a game mode, such as whether it is active, available, or in a particular operational phase.
-
B.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
C.
hasChallengeMode
Indicates that an entity offers or is associated with a special, typically more difficult, challenge-oriented mode or setting.
-
D.
hasKillstreakSupport
Indicates that an entity provides or is associated with special support actions or benefits that become available when another entity achieves a killstreak.
-
E.
hasMatchmakingSystem
Indicates that an entity includes or is associated with a system that pairs or connects participants based on defined criteria.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69ff90b5b98881909620033d78e4a9b8 |
completed | May 9, 2026, 7:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.