Triple
T35540335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PR-15 Ragun |
E1027041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fictional entity |
C47979
|
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 entity Context triple: [PR-15 Ragun, instanceOf, Fictional entity]
-
A.
fictional element
A fictional element is an invented chemical substance, often with unique properties or powers, created for use in stories, games, or speculative settings.
-
B.
entity in a fictional universe
chosen
An entity in a fictional universe is any distinct being, object, or construct that exists within the imagined setting and participates in or is affected by its narrative, rules, and events.
-
C.
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.
-
D.
fictional company
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.
-
E.
fictional phenomenon
A fictional phenomenon is an imagined event, process, or occurrence that exists only within the context of a narrative or invented world, governed by that setting’s own internal logic rather than real-world science.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.