Triple
T23201180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warhammer tabletop gaming |
E580016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tabletop wargame franchise |
C17518
|
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: tabletop wargame franchise Context triple: [Warhammer tabletop gaming, instanceOf, tabletop wargame franchise]
-
A.
military wargame
A military wargame is a simulated conflict scenario used to model, analyze, and train for real or hypothetical military operations, strategies, and decision-making.
-
B.
Warhammer 40,000 faction
A Warhammer 40,000 faction is a distinct, lore-rich army or group within the setting’s galaxy-spanning conflict, defined by unique aesthetics, units, rules, and narrative themes that shape how it plays on the tabletop and in the story.
-
C.
tabletop game
chosen
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.
-
D.
warlord conflict
A warlord conflict is a power struggle in which armed leaders, often commanding private militias, compete for territorial control, resources, and political authority in the absence or weakness of a central state.
-
E.
warlord army
A warlord army is a militarized force loyal to a single powerful leader, often operating outside formal state control and sustained through conquest, coercion, and resource extraction.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:06 p.m.