Triple
T29548196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyalist Committee |
E749686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organization in the Galactic Republic |
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: organization in the Galactic Republic Context triple: [Loyalist Committee, instanceOf, organization in the Galactic Republic]
-
A.
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.
-
B.
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.
-
C.
region in the Star Wars galaxy
A region in the Star Wars galaxy is a large-scale spatial division of known space, encompassing multiple star systems, sectors, and hyperspace routes that share common political, cultural, or navigational characteristics.
-
D.
Trade Federation official
A Trade Federation official is a high-ranking administrator responsible for overseeing the organization’s commercial policies, negotiations, and enforcement of trade regulations across its controlled territories.
-
E.
Rebel Alliance member
A Rebel Alliance member is an individual who actively opposes the Galactic Empire by participating in organized resistance efforts to restore freedom and justice to the galaxy.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:09 p.m.