Triple
T10673028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | subsumption architecture |
E251542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | robotics control architecture |
C21609
|
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: robotics control architecture Context triple: [subsumption architecture, instanceOf, robotics control architecture]
-
A.
robot control system
chosen
A robot control system is a coordinated set of hardware and software components that interpret sensor data, execute decision-making algorithms, and generate actuator commands to direct a robot’s behavior in real time.
-
B.
robotics actuator
A robotics actuator is a device that converts energy (such as electrical, hydraulic, or pneumatic power) into controlled mechanical motion to drive the movement of robotic components.
-
C.
export control law
Export control law is the body of legal rules and regulations that govern the transfer of goods, technology, software, and services across national borders to protect national security, foreign policy interests, and international obligations.
-
D.
Android-based robot controller
An Android-based robot controller is a software component running on an Android device that provides a user interface and communication layer to send commands to, receive feedback from, and manage the behavior of a connected robot system.
-
E.
robotics program
A robotics program is a structured course or initiative that teaches the design, construction, and programming of robots to solve real-world problems or complete specific tasks.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.