Triple
T35647670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romulan–Federation conflicts |
E1030053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional interstellar conflict |
C10308
|
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 interstellar conflict Context triple: [Romulan–Federation conflicts, instanceOf, fictional interstellar conflict]
-
A.
fictional interstellar war
chosen
A fictional interstellar war is a large-scale, imagined conflict between civilizations or factions across multiple star systems, often involving advanced technology, alien species, and complex political or ideological struggles.
-
B.
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.
-
C.
fictional alien civilization
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.
-
D.
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.
-
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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.