Triple
T20391298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Brewster |
E498090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Terminator character |
C43987
|
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: Terminator character Context triple: [Kate Brewster, instanceOf, Terminator character]
-
A.
character in the Robot series
A character in the Robot series is an individual—human, robot, or other sentient entity—whose actions, decisions, and interactions drive the exploration of robotics, ethics, and society within Asimov’s interconnected universe.
-
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.
Starship Troopers character
A Starship Troopers character is an individual—human or alien—who exists within the militaristic, satirical sci-fi universe of Starship Troopers, defined by their role in interstellar warfare, political ideology, and interactions with the series’ themes of duty, citizenship, and propaganda.
-
D.
Transformers character
A Transformers character is a sentient robotic being from the Transformers universe, typically capable of transforming between a humanoid robot form and an alternate mode such as a vehicle, weapon, or creature, with distinct allegiance, personality, and abilities.
-
E.
Top Gun character
A Top Gun character is a highly skilled, larger-than-life naval aviator or associated figure whose personality, relationships, and aerial combat prowess drive the drama and action within the Top Gun universe.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.