Triple
T37011997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gears Tactics |
E915975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turn-based tactics game |
C61928
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: turn-based tactics game Context triple: [Gears Tactics, instanceOf, turn-based tactics game]
-
A.
turn-based strategy game
A turn-based strategy game is a type of game where players take discrete, alternating turns to make tactical and strategic decisions—such as moving units, managing resources, and executing actions—in order to outmaneuver and defeat opponents.
-
B.
turn-based strategy game series
A turn-based strategy game series is a collection of related games in which players take discrete, alternating turns to make tactical and strategic decisions, often managing resources, units, and territories over multiple scenarios or campaigns.
-
C.
squad-based tactics game
chosen
A squad-based tactics game is a strategy game where players control a small team of individual units, each with distinct abilities, to complete objectives through careful positioning, coordinated actions, and turn- or time-based decision-making.
-
D.
tabletop game
A tabletop game is a structured form of play conducted on a flat surface using physical components such as boards, cards, dice, or miniatures, governed by explicit rules and typically involving two or more players.
-
E.
strategy game mode
A strategy game mode is a configurable ruleset or scenario within a game that emphasizes planning, resource management, and tactical decision-making to achieve specific objectives.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.