Triple
T29391282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adafruit Feather M0 boards |
E745373
|
entity |
| Predicate | inputVoltageRange |
P83887
|
FINISHED |
| Object | USB 5V |
—
|
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 5V | Statement: [Adafruit Feather M0 boards, inputVoltageRange, USB 5V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputVoltageRange Context triple: [Adafruit Feather M0 boards, inputVoltageRange, USB 5V]
-
A.
supplyVoltageRange
Indicates the range of electrical supply voltages within which the entity is designed or allowed to operate.
-
B.
typicalVoltageRange
Indicates the usual minimum-to-maximum voltage interval within which something is designed or expected to operate.
-
C.
typicalSupplyVoltageRange
chosen
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
-
D.
typicalSupplyVoltage
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
-
E.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 2:42 p.m.