Triple
T38218614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Colonial Marine Corps |
E1010749
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional space force |
C17673
|
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 space force Context triple: [United States Colonial Marine Corps, instanceOf, fictional space force]
-
A.
fictional interstellar war
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 space exploration organization
chosen
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.
-
C.
space Western
A space Western is a genre that blends the frontier themes, archetypes, and aesthetics of classic Westerns with futuristic settings, technology, and interstellar adventure.
-
D.
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.
-
E.
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.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.