Triple
T29870722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxxon Energy Corporation |
E758587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional energy company |
C7523
|
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 energy company Context triple: [Roxxon Energy Corporation, instanceOf, fictional energy company]
-
A.
fictional company
chosen
A fictional company is an imagined business entity created for storytelling, simulation, or illustrative purposes, complete with its own brand, structure, and operations but without real-world legal or commercial existence.
-
B.
fictional power plant
A fictional power plant is an imagined facility that generates and distributes energy within a narrative world, often using speculative technologies or fantastical resources to power societies, devices, or plot events.
-
C.
fictional corporate office
A fictional corporate office is an imagined workplace setting that represents the structure, culture, and daily operations of a business organization, often used as a backdrop for storytelling, satire, or exploration of professional dynamics.
-
D.
fictional factory
A fictional factory is an imagined industrial facility, often depicted in stories or media, where goods, ideas, or fantastical items are produced under unique or extraordinary conditions.
-
E.
fictional legal person
A fictional legal person is an entity, such as a corporation or organization, that the law recognizes as having legal rights and responsibilities similar to those of a natural person, despite not being a human being.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:53 p.m.