Triple
T4176725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Box |
E86494
|
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 Box, 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.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:45 p.m.