Triple
T16785009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quill |
E407948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | species in the Doctor Who universe |
C38020
|
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: species in the Doctor Who universe Context triple: [Quill, instanceOf, species in the Doctor Who universe]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Torchwood character
A Torchwood character is an individual—human, alien, or otherwise—who plays a role in the secretive, extraterrestrial-investigating Torchwood Institute universe, contributing to its stories of covert operations, moral ambiguity, and encounters with the unknown.
-
E.
Gallifreyan organization
A Gallifreyan organization is a structured collective of Time Lords and associated entities from the planet Gallifrey, formed to govern, regulate, or influence temporal affairs and societal functions within Time Lord civilization.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.