Triple
T6868516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luke Smith |
E158478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Doctor Who universe character |
C12701
|
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 universe character Context triple: [Luke Smith, instanceOf, Doctor Who universe character]
-
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.
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.
-
C.
Doctor Who companion
chosen
A Doctor Who companion is a character who travels with the Doctor, providing emotional grounding, narrative perspective, and active assistance in adventures across time and space.
-
D.
Torchwood operative
A Torchwood operative is a covert agent working for the secretive Torchwood Institute, tasked with investigating, containing, and exploiting extraterrestrial and supernatural phenomena to protect Earth.
-
E.
Star Trek character
A Star Trek character is an individual—human, alien, or artificial—who exists within the Star Trek universe and contributes to its stories through their role, relationships, and development across various series and films.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:22 p.m.