Triple
T32613872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LV-223 |
E833732
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical body in fiction |
C4944
|
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 body in fiction Context triple: [LV-223, instanceOf, astronomical body in fiction]
-
A.
astronomical location in fiction
An astronomical location in fiction is a narrative setting situated in outer space—such as planets, moons, stars, space stations, or other cosmic environments—used to frame events, characters, and plots within a speculative or imaginative universe.
-
B.
fictional planet
chosen
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.
-
C.
astronomical object
An astronomical object is any naturally occurring physical entity in space, such as stars, planets, moons, asteroids, comets, or galaxies, that exists within the universe.
-
D.
fictional comet
A fictional comet is an imagined celestial body, often with unique properties or narrative significance, that travels through space and influences events or characters within a story’s universe.
-
E.
entity in a fictional universe
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.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:06 a.m.