Triple
T3538362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaeger |
E74820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional combat robot |
C5782
|
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: fictional combat robot Context triple: [Jaeger, instanceOf, fictional combat robot]
-
A.
fictional robot
chosen
A fictional robot is an imagined artificial being, typically mechanical or digital, designed with varying degrees of intelligence and autonomy to perform tasks, interact with characters, or explore themes about technology and humanity in stories.
-
B.
giant humanoid mecha
A giant humanoid mecha is a towering, human-shaped robotic vehicle typically piloted by one or more operators, designed for large-scale combat, defense, or heavy-duty tasks.
-
C.
cybernetically augmented humanoids
Cybernetically augmented humanoids are beings whose biological bodies are enhanced or partially replaced with advanced technological systems to expand their physical, cognitive, or sensory capabilities beyond natural human limits.
-
D.
robot
A robot is an autonomous or semi-autonomous machine capable of sensing its environment, processing information, and performing physical or virtual tasks, often programmable to adapt to different functions.
-
E.
video game fictional entity
A video game fictional entity is any imagined character, creature, object, or construct that exists within the narrative or interactive world of a video game, defined by its designed attributes, behaviors, and role in gameplay or story.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:20 p.m.