Triple
T38476899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firing Range |
E915572
|
entity |
| Predicate | hasGameModeSupport |
P69305
|
FINISHED |
| Object | Team Deathmatch |
—
|
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: Team Deathmatch | Statement: [Firing Range, hasGameModeSupport, Team Deathmatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameModeSupport Context triple: [Firing Range, hasGameModeSupport, Team Deathmatch]
-
A.
hasPrimaryModeSupported
Indicates that an entity supports a particular mode as its main or default mode of operation.
-
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.
hasModeSystem
Indicates that one entity operates under, or is associated with, a particular mode defined or managed by another system.
-
E.
appearsInGameMode
chosen
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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:31 p.m.