Triple
T29391255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adafruit Feather M0 boards |
E745373
|
entity |
| Predicate | basedOnMicrocontroller |
P34286
|
FINISHED |
| Object | Microchip ATSAMD21G18 |
—
|
NE NERFINISHED |
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: Microchip ATSAMD21G18 | Statement: [Adafruit Feather M0 boards, basedOnMicrocontroller, Microchip ATSAMD21G18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnMicrocontroller Context triple: [Adafruit Feather M0 boards, basedOnMicrocontroller, Microchip ATSAMD21G18]
-
A.
hasMicrocontroller
chosen
Indicates that an entity contains, includes, or is equipped with a microcontroller as one of its components.
-
B.
hasMicrocontrollerCore
Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
-
C.
hasDevelopmentBoard
Indicates that an entity is associated with, or supported by, a specific development board used for building or testing hardware or software.
-
D.
coreBasedOn
Indicates that one entity is fundamentally derived from, built upon, or primarily based on another entity.
-
E.
mcuPower
Indicates that one entity supplies, controls, or is responsible for the electrical power provided to a microcontroller unit (MCU).
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 2:42 p.m.