Triple
T29391704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arduino-based robots |
E745382
|
entity |
| Predicate | typicalBoard |
P49862
|
FINISHED |
| Object | Arduino Uno |
E1276844
|
NE 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: Arduino Uno | Statement: [Arduino-based robots, typicalBoard, Arduino Uno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBoard Context triple: [Arduino-based robots, typicalBoard, Arduino Uno]
-
A.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
B.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
C.
usesBoardShape
Indicates that one entity employs or is designed to work with a particular board shape as part of its function or configuration.
-
D.
typicalBase
chosen
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
E.
boardProperties
Indicates a relationship where specific attributes or characteristics are assigned to or associated with a board.
- F. None of above.
Provenance (4 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25c1156db481909585379f2b8db5e4 |
completed | June 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
Created at: April 28, 2026, 2:42 p.m.