Triple
T10920130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Room program |
E257925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional covert training program |
C24855
|
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 covert training program Context triple: [Red Room program, instanceOf, fictional covert training program]
-
A.
fictional military program
chosen
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.
CIA program
A CIA program is an organized, often covert initiative or operation designed and managed by the Central Intelligence Agency to achieve specific intelligence, security, or foreign policy objectives.
-
C.
spy training school
A spy training school is a covert institution that rigorously prepares recruits in espionage skills such as surveillance, disguise, cryptography, and intelligence gathering for clandestine operations.
-
D.
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.
-
E.
CIA front company
A CIA front company is a seemingly legitimate business entity secretly created or controlled by the Central Intelligence Agency to provide cover, funding, logistics, or operational support for intelligence activities without revealing government involvement.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.