Triple
T31103633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bene Gesserit |
E792738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organization in the Dune universe |
C59575
|
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 Dune universe Context triple: [Bene Gesserit, instanceOf, organization in the Dune universe]
-
A.
title in the Dune universe
A title in the Dune universe is a formal designation or rank—such as Duke, Reverend Mother, or Padishah Emperor—that signifies an individual’s political, religious, or social authority within its feudal, interstellar society.
-
B.
Dune novel
A Dune novel is a science fiction book set in a complex, futuristic universe centered on the desert planet Arrakis, exploring themes of politics, ecology, religion, and power through the struggles of its characters.
-
C.
Dune character
A Dune character is an individual entity within the Dune universe, defined by distinct traits, roles, and relationships that drive the saga’s political, ecological, and spiritual narratives.
-
D.
character in the Foundation series
A character in the Foundation series is an individual—human, robot, or otherwise—whose actions, beliefs, and relationships shape the political, social, and psychological evolution of Isaac Asimov’s galactic civilization.
-
E.
event in the Foundation universe
An event in the Foundation universe is a significant occurrence or incident—such as a mission, anomaly breach, discovery, or containment operation—that alters the status quo of the Foundation, its personnel, or the anomalies it manages.
- F. None of above. chosen
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.