Triple
T28889819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retreat from Osgiliath |
E732665
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional military engagement |
C7050
|
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 engagement Context triple: [Retreat from Osgiliath, instanceOf, fictional military engagement]
-
A.
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.
-
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.
military confrontation
chosen
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
D.
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.
-
E.
covert military conflict
A covert military conflict is a hidden or plausibly deniable struggle between states or organized groups that uses clandestine operations, proxies, and intelligence activities instead of overt, declared warfare.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:54 a.m.