Triple
T35690773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentes system |
E1031283
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical object in the Star Wars universe |
C596
|
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: astronomical object in the Star Wars universe Context triple: [Gentes system, instanceOf, astronomical object in the Star Wars universe]
-
A.
era in the Star Wars universe
An era in the Star Wars universe is a distinct span of in-universe time characterized by specific galactic events, political powers, and cultural conditions that define the setting for stories and conflicts.
-
B.
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.
-
C.
astronomical object
chosen
An astronomical object is any naturally occurring physical entity in space, such as stars, planets, moons, asteroids, comets, or galaxies, that exists within the universe.
-
D.
weapon in the Star Wars universe
A weapon in the Star Wars universe is any tool or device—ranging from primitive melee arms to advanced energy-based and superweapons—designed to inflict damage, exert control, or provide defense within the galaxy’s technological and mystical context.
-
E.
in-universe object
An in-universe object is any tangible or intangible item that exists within a fictional world's reality and can be perceived, used, or referenced by characters in that setting.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.