Triple
T29012794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadreck |
E737212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lensman character |
C55522
|
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: Lensman character Context triple: [Nadreck, instanceOf, Lensman character]
-
A.
Terminator character
A Terminator character is a relentless, human-like cyborg assassin from the future, typically sent back in time with a specific mission that often pits advanced machine intelligence against human survival.
-
B.
Cyberman leader
A Cyberman leader is the commanding figure among Cybermen who directs their collective actions, strategies, and conversions with enhanced authority and tactical intelligence.
-
C.
MonsterVerse character
A MonsterVerse character is a fictional being—often a giant monster, titan, or associated human figure—originating from the shared cinematic universe that includes Godzilla, Kong, and related creatures, defined by its role within that interconnected storyline.
-
D.
Tron character
A Tron character is a stylized, neon-lit digital persona existing within a computer-generated world, embodying programs, users, or security forces that interact through high-tech combat and light-based vehicles.
-
E.
Jules Verne character
A Jules Verne character is a fictional person, creature, or entity appearing in the adventure and science fiction narratives of French author Jules Verne, often embodying themes of exploration, innovation, and the limits of human knowledge.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:43 a.m.