Triple
T10673029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | subsumption architecture |
E251542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | behavior-based robotics paradigm |
C28833
|
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: behavior-based robotics paradigm Context triple: [subsumption architecture, instanceOf, behavior-based robotics paradigm]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
joint planning and execution system
A joint planning and execution system is an integrated framework that enables multiple agents or stakeholders to collaboratively create, coordinate, and carry out shared plans toward common goals in dynamic environments.
-
E.
robotics research platform
A robotics research platform is a configurable hardware and software system designed to develop, test, and evaluate robotic algorithms, sensors, and control strategies in controlled and repeatable environments.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.