Triple

T37503784
Position Surface form Disambiguated ID Type / Status
Subject Battlemode E932038 entity
Predicate supportsCustomLoadouts P205932 FINISHED
Object limited 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: limited | Statement: [Battlemode, supportsCustomLoadouts, limited]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsCustomLoadouts
Context triple: [Battlemode, supportsCustomLoadouts, limited]
  • A. supportsCloudSaves
    Indicates that one entity provides functionality for storing and retrieving save data in the cloud for another entity.
  • B. supportsModding
    Indicates that one entity provides the capability or infrastructure for another entity to be modified or extended by users (e.g., via mods or custom content).
  • C. loadoutSlot
    Indicates the specific equipment or item slot in which a particular piece of gear or object is placed within a loadout configuration.
  • D. supportsWeaponTuning
    Indicates that an entity provides the capability to adjust, modify, or customize the characteristics or performance of a weapon.
  • E. supportsInvasionMultiplayer
    Indicates that a game or system allows and is compatible with invasion-style multiplayer gameplay, where other players can enter and disrupt one’s session.
  • 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_69f76ec5268481909ea01c73aeeefd42 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037cad051c8190b28b354b89208574 completed May 12, 2026, 7:17 p.m.
PD Predicate disambiguation batch_6a037a1553e08190bb7424c448cb1f33 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c842b2c819082f1d2db995ac2eb completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:17 p.m.