Triple
T29893696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial High Command |
E759220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Galactic Empire institution |
C23323
|
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: Galactic Empire institution Context triple: [Imperial High Command, instanceOf, Galactic Empire institution]
-
A.
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.
-
B.
Gallifreyan organization
A Gallifreyan organization is a structured collective of Time Lords and associated entities from the planet Gallifrey, formed to govern, regulate, or influence temporal affairs and societal functions within Time Lord civilization.
-
C.
Trade Federation world
A Trade Federation world is a planet or system primarily governed and economically dominated by a powerful interstellar trade consortium, where commerce, shipping routes, and corporate interests shape its politics, society, and infrastructure.
-
D.
Star Wars organization
chosen
A Star Wars organization is a structured group or faction within the Star Wars universe, defined by a common purpose, ideology, or function that influences galactic events and character relationships.
-
E.
in-universe organization
An in-universe organization is a fictional group, institution, or entity that operates within a story’s setting, shaping events, characters, and world dynamics according to its goals, structure, and culture.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:03 p.m.