Triple
T29391291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adafruit Feather M0 boards |
E745373
|
entity |
| Predicate | hasAnalogInputs |
P71412
|
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, hasAnalogInputs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnalogInputs Context triple: [Adafruit Feather M0 boards, hasAnalogInputs, yes]
-
A.
hasAnalogInputChannels
chosen
Indicates that an entity is equipped with one or more channels capable of receiving analog input signals.
-
B.
hasAnalog
Indicates that one entity corresponds to or functions similarly to another entity in a comparable context or role.
-
C.
isAnalogOrDigital
Indicates whether something operates using analog signals/representation or digital signals/representation.
-
D.
supportsAnalogOnly
Indicates that the subject provides or is compatible only with analog functionality, and does not support any digital capabilities.
-
E.
analogChannel
Indicates a relationship where a channel carries or transmits signals in analog (continuously varying) form rather than digital form.
- 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_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 2:42 p.m.