Triple
T16682908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sash of Rassilon |
E405383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in the Doctor Who universe |
C4485
|
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: object in the Doctor Who universe Context triple: [The Sash of Rassilon, instanceOf, object in the Doctor Who universe]
-
A.
Object from Doctor Who
chosen
An Object from Doctor Who is any in-universe item, device, artifact, or construct—often with advanced, alien, or time-travel-related properties—that characters interact with to drive the plot or explore the show's science-fiction concepts.
-
B.
location in the Doctor Who universe
A "location in the Doctor Who universe" is any distinct place—planet, spaceship, dimension, time period, or specific site—where events, characters, or stories from Doctor Who occur or are referenced.
-
C.
character from Doctor Who
A character from Doctor Who is an individual—human, alien, or otherwise—who exists within the Doctor Who universe and participates in its time-traveling, science-fiction narratives.
-
D.
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.
-
E.
location in the Torchwood universe
A "location in the Torchwood universe" is any distinct place—on Earth, in space, or across time—where events, organizations, or characters from Torchwood exist or act, such as cities, alien worlds, hidden bases, or temporal anomalies.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.