Triple
T16000094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XCOM series |
E388070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turn-based tactics franchise |
C34192
|
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 franchise Context triple: [XCOM series, instanceOf, turn-based tactics franchise]
-
A.
turn-based strategy game series
chosen
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.
-
B.
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.
-
C.
action role-playing game series
An action role-playing game series is a collection of related video games that blend real-time combat and character control with role-playing elements such as character progression, narrative choices, and equipment customization across multiple interconnected titles.
-
D.
Capcom franchise
A Capcom franchise is a series of related video games and associated media developed or published by Capcom, typically sharing common characters, settings, and gameplay themes.
-
E.
fighting game series
A fighting game series is a collection of related video games centered on competitive combat between characters, typically featuring recurring fighters, mechanics, and story elements across multiple installments.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:55 a.m.