Triple
T14639217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daenerys Targaryen's conquest of Slaver's Bay |
E343680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military campaign |
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 Context triple: [Daenerys Targaryen's conquest of Slaver's Bay, instanceOf, fictional military campaign]
-
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 interstellar war
A fictional interstellar war is a large-scale, imagined conflict between civilizations or factions across multiple star systems, often involving advanced technology, alien species, and complex political or ideological struggles.
-
C.
military campaign theater
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
-
D.
fictionalEvent
chosen
A fictionalEvent represents an invented occurrence or happening within a narrative world, defined by its time, place, participants, and narrative significance.
-
E.
fictional plan
A fictional plan is an imagined, often detailed strategy or course of action that exists only within a narrative, scenario, or conceptual context rather than in real-world implementation.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.