Triple
T27554280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battles of the Fords of Isen |
E695591
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military campaign account |
C11373
|
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 military campaign account Context triple: [The Battles of the Fords of Isen, instanceOf, fictional military campaign account]
-
A.
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.
-
B.
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.
-
C.
historical adventure fiction
Historical adventure fiction is a genre that blends meticulously researched past settings and events with fast-paced, often perilous journeys or quests, emphasizing action, exploration, and personal heroism within a specific historical context.
-
D.
World War II novel
A World War II novel is a work of fiction set during the Second World War that explores the experiences, struggles, and moral complexities of individuals or societies affected by the global conflict.
-
E.
fictionalEvent
chosen
A fictionalEvent represents an invented occurrence or happening within a narrative world, defined by its time, place, participants, and narrative significance.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:36 p.m.