Triple
T30389110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEGO Mindstorms programming language |
E773022
|
entity |
| Predicate | communicationWithRobot |
P40250
|
FINISHED |
| Object | USB |
—
|
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: USB | Statement: [LEGO Mindstorms programming language, communicationWithRobot, USB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationWithRobot Context triple: [LEGO Mindstorms programming language, communicationWithRobot, USB]
-
A.
robotFunction
Indicates the specific role, task, or operational purpose that a robot is designed or configured to perform.
-
B.
communicationFunction
Indicates that one entity serves a communicative role or purpose in relation to another, such as conveying, mediating, or facilitating the exchange of information.
-
C.
communicationRelayCapability
Indicates that an entity has the ability to relay or forward communications between other entities or systems.
-
D.
communicatesTo
chosen
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
E.
robotPrimeDirective
Indicates that a robot is governed by a fundamental guiding rule or set of rules that constrain and direct its actions and decisions.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:02 p.m.