Triple
T29391285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adafruit Feather M0 boards |
E745373
|
entity |
| Predicate | supportsSleepModes |
P99857
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Adafruit Feather M0 boards, supportsSleepModes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSleepModes Context triple: [Adafruit Feather M0 boards, supportsSleepModes, yes]
-
A.
powerManagementFeatures
Indicates that one entity provides, supports, or is associated with capabilities for controlling, optimizing, or conserving the power usage of another entity.
-
B.
hasSleepCoverAccessory
Indicates that an entity is equipped with or includes an accessory specifically intended for use during sleep.
-
C.
supportsObservationModes
Indicates that one entity provides or is compatible with specific modes or methods of observation used by another entity.
-
D.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
E.
supportsLowVoltageMode
Indicates that an entity is capable of operating correctly in, or providing functionality for, a reduced or low-voltage operating mode.
- 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_6a0352b6c7dc81908f190060eb1e1857 |
completed | May 12, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_6a03507c37d4819091068b2ec5cacef9 |
completed | May 12, 2026, 4:08 p.m. |
Created at: April 28, 2026, 2:42 p.m.