Triple
T22020405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle against Mimics at Verdun (novel continuity) |
E543829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in a fictional universe |
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: event in a fictional universe Context triple: [Battle against Mimics at Verdun (novel continuity), instanceOf, event in a fictional universe]
-
A.
event in a work of fiction
An event in a work of fiction is a discrete occurrence or happening within the narrative that causes change, advances the plot, or reveals character or theme.
-
B.
fictionalEvent
chosen
A fictionalEvent represents an invented occurrence or happening within a narrative world, defined by its time, place, participants, and narrative significance.
-
C.
fictional universe
A fictional universe is a self-contained, invented reality with its own consistent settings, rules, characters, and histories in which stories take place.
-
D.
event in the Star Wars universe
An event in the Star Wars universe is a significant occurrence or incident—such as a battle, political decision, personal confrontation, or galactic-scale crisis—that alters the state of characters, factions, or the broader timeline within the Star Wars narrative.
-
E.
fictional phenomenon
A fictional phenomenon is an imagined event, process, or occurrence that exists only within the context of a narrative or invented world, governed by that setting’s own internal logic rather than real-world science.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:23 p.m.