Triple
T37503789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlemode |
E932038
|
entity |
| Predicate | supportsVoiceChat |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVoiceChat Context triple: [Battlemode, supportsVoiceChat, yes]
-
A.
supportsVoIP
chosen
Indicates that one entity provides the capability for Voice over IP (VoIP) communication to or for another entity.
-
B.
haveRichVoiceSystem
Indicates that an entity possesses a voice system characterized by richness, such as depth, fullness, or expressive quality.
-
C.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
D.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
E.
supportsVideoCalling
Indicates that one entity provides or enables video calling functionality for another entity.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:17 p.m.