Triple
T22513166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volm Collective |
E556571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional alien alliance |
C40051
|
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 alien alliance Context triple: [Volm Collective, instanceOf, fictional alien alliance]
-
A.
fictional alien civilization
chosen
A fictional alien civilization is an imagined society of non-human, extraterrestrial beings with its own distinct biology, culture, technology, and social structures, often used to explore alternative forms of life and societal organization.
-
B.
fictional interstellar government
A fictional interstellar government is a large-scale political organization that exerts authority, creates laws, and manages relations across multiple planets, star systems, or galaxies within a speculative universe.
-
C.
fictional galactic empire
A fictional galactic empire is a vast, often authoritarian interstellar civilization that spans multiple star systems, exerting political, military, and cultural control across the galaxy.
-
D.
fictional space exploration organization
A fictional space exploration organization is an imagined institution—such as an agency, corporation, or coalition—dedicated to planning, funding, and conducting missions beyond Earth for purposes like discovery, colonization, defense, or scientific advancement.
-
E.
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.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.