Triple
T17866608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bajor system |
E446719
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical location in fiction |
C39226
|
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: astronomical location in fiction Context triple: [Bajor system, instanceOf, astronomical location in fiction]
-
A.
fictional planet
A fictional planet is an imagined celestial world, often with its own unique geography, ecosystems, cultures, and physical laws, created to serve as the setting for stories or speculative scenarios.
-
B.
fictional galaxy
A fictional galaxy is an imagined, large-scale cosmic setting composed of stars, planets, civilizations, and phenomena that serves as a backdrop for storytelling in speculative fiction.
-
C.
location in the Foundation universe
A "location in the Foundation universe" represents any distinct physical or spatial setting—such as planets, space stations, sectors, or regions—within the fictional cosmos of Isaac Asimov’s Foundation series, characterized by its geography, political affiliation, culture, and narrative significance.
-
D.
region in the Star Wars galaxy
A region in the Star Wars galaxy is a large-scale spatial division of known space, encompassing multiple star systems, sectors, and hyperspace routes that share common political, cultural, or navigational characteristics.
-
E.
astronomical region
An astronomical region is a defined area of space, often delineated by physical, observational, or conceptual boundaries, used to study and describe the distribution and behavior of celestial objects and phenomena.
- F. None of above. chosen
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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:17 a.m.