Triple
T29548145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightsaber combat |
E749685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional combat discipline |
C39455
|
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: fictional combat discipline Context triple: [Lightsaber combat, instanceOf, fictional combat discipline]
-
A.
fictional martial art
chosen
A fictional martial art is an invented combat system, often blending stylized physical techniques with unique philosophies, powers, or cultural elements, created to enrich the worldbuilding of stories, games, or other imaginative media.
-
B.
fictional military program
A fictional military program is an imagined, often secretive initiative or project within an armed forces setting, designed to explore advanced technologies, strategies, or operations that drive the narrative in speculative or military-themed stories.
-
C.
fictional military siege
A fictional military siege is a prolonged, often strategically complex encirclement and assault on a fortified location within a narrative, used to create tension, test characters, and explore themes of endurance, sacrifice, and conflict.
-
D.
fictional faction
A fictional faction is an organized group within a narrative world, defined by shared goals, beliefs, and identity that influence the story’s conflicts and alliances.
-
E.
military training doctrine
A military training doctrine is a formalized set of principles, methods, and standards that guides how armed forces prepare personnel and units to plan, fight, and support operations effectively and consistently.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:09 p.m.