Triple
T27872085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D’Qar |
E704816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | celestial body in the Star Wars universe |
C14415
|
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: celestial body in the Star Wars universe Context triple: [D’Qar, instanceOf, celestial body in the Star Wars universe]
-
A.
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.
-
B.
concept in the Star Wars universe
A concept in the Star Wars universe is an abstract idea, principle, or phenomenon—such as the Force, the Jedi Code, or hyperspace—that shapes the lore, culture, and conflicts of the galaxy far, far away.
-
C.
event in the Star Wars universe
An event in the Star Wars universe is a significant occurrence or incident—such as a battle, political decision, personal confrontation, or galactic-scale crisis—that alters the state of characters, factions, or the broader timeline within the Star Wars narrative.
-
D.
title in the Star Wars universe
A title in the Star Wars universe is an honorific or rank designation that signifies a character’s role, status, or authority within its political, military, religious, or criminal hierarchies (e.g., Jedi Master, Sith Lord, Grand Moff).
-
E.
in-universe object
chosen
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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 6:25 p.m.