Triple
T20367840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antal Bejczy Center for Intelligent Robotics |
E496961
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | robotics research center |
C26945
|
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 research center Context triple: [Antal Bejczy Center for Intelligent Robotics, instanceOf, robotics research center]
-
A.
robotics research laboratory
chosen
A robotics research laboratory is a specialized facility where researchers design, build, program, and experimentally evaluate robotic systems and related technologies to advance automation and intelligent behavior.
-
B.
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.
-
C.
work on robotics
Work on robotics encompasses the research, design, development, and application of robotic systems that sense, decide, and act to perform tasks autonomously or in collaboration with humans.
-
D.
computer science research center
A computer science research center is an institution dedicated to advancing knowledge and innovation in computing through focused research, collaboration, and dissemination of results across areas such as algorithms, systems, artificial intelligence, and human-computer interaction.
-
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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:26 a.m.