Triple
T25075081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xnet |
E628022
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional communication network |
C33703
|
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 communication network Context triple: [Xnet, instanceOf, fictional communication network]
-
A.
fictional data network
chosen
A fictional data network is an imagined system of interconnected digital nodes and channels that facilitates the exchange, processing, and storage of information within a speculative or narrative context.
-
B.
fictional transportation network
A fictional transportation network is an imagined system of interconnected routes, vehicles, and hubs that enables the movement of people or goods within a speculative or invented setting.
-
C.
fictional computer
A fictional computer is an imagined computing device, often with advanced or impossible capabilities, that exists only within stories, games, or speculative scenarios.
-
D.
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.
-
E.
fictional device
A fictional device is an imagined tool, machine, or piece of technology that does not exist in reality but is created within a narrative to serve specific plot, thematic, or world-building purposes.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:21 a.m.