Triple
T10672774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rethink Robotics |
E251535
|
entity |
| Predicate | robotApplication |
P82955
|
FINISHED |
| Object | assembly |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: assembly | Statement: [Rethink Robotics, robotApplication, assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: robotApplication Context triple: [Rethink Robotics, robotApplication, assembly]
-
A.
robotFunction
chosen
Indicates the specific role, task, or operational purpose that a robot is designed or configured to perform.
-
B.
robotType
Indicates the specific category or kind of robot that an entity belongs to.
-
C.
exampleApplication
Indicates that something serves as a representative or illustrative instance of how an application is used or functions.
-
D.
hasRobot
Indicates that one entity possesses, controls, or is associated with a robot.
-
E.
robotControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the actions and behaviors of one or more robots.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69d6f8659d40819087a2709bd24261ee |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.