Triple
T17017339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Shoreditch, London, 1963) |
E412856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Doctor Who setting |
C37285
|
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: Doctor Who setting Context triple: [Earth (Shoreditch, London, 1963), instanceOf, Doctor Who setting]
-
A.
location in the Doctor Who universe
chosen
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.
-
B.
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.
-
C.
species in the Doctor Who universe
A species in the Doctor Who universe is a distinct sentient or non-sentient lifeform, often with unique physiology, culture, abilities, and history, that inhabits or originates from a particular planet, dimension, or point in time.
-
D.
Time Lord city
A Time Lord city is a vast, technologically and temporally advanced urban center designed to support, govern, and protect the Time Lords and their time-manipulating civilization.
-
E.
Object from Doctor Who
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.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.