Triple
T36347459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan tracking network |
E895104
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional surveillance system |
C13393
|
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 surveillance system Context triple: [Titan tracking network, instanceOf, fictional surveillance system]
-
A.
electronic surveillance program
chosen
An electronic surveillance program is a system that monitors, collects, and analyzes digital communications or electronic data to detect, track, or investigate activities of interest, often for security, intelligence, or law enforcement purposes.
-
B.
work on digital surveillance
Work on digital surveillance examines the technologies, practices, and power structures involved in monitoring, collecting, and analyzing individuals’ data in digital environments and their social, ethical, and legal implications.
-
C.
fictional cyborg
A fictional cyborg is a being that combines organic life with mechanical or electronic enhancements, often exploring themes of identity, humanity, and the boundary between man and machine.
-
D.
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.
-
E.
fictional neural interface system
A fictional neural interface system is an imagined technology that directly links the human brain with computers or networks to enable seamless communication, control, and data exchange through thought alone.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.