Triple
T29391281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adafruit Feather M0 boards |
E745373
|
entity |
| Predicate | logicLevel |
P167141
|
FINISHED |
| Object | 3.3V |
—
|
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: 3.3V | Statement: [Adafruit Feather M0 boards, logicLevel, 3.3V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicLevel Context triple: [Adafruit Feather M0 boards, logicLevel, 3.3V]
-
A.
logicLevelDetermines
Indicates that the specific logic level of one entity determines or dictates the resulting state, behavior, or outcome of another entity.
-
B.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
C.
logicLevelForInactive
Indicates the signal level (e.g., high or low) that represents the inactive or deasserted state of a logic signal or control line.
-
D.
logicType
Indicates the specific kind or category of logical system, rule, or reasoning framework that an entity or statement belongs to.
-
E.
signalLevel
Indicates the intensity or strength of a transmitted or received signal in a communication context.
- F. None of above. chosen
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_69f669ff3b2081909ecfc701841c6532 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 2:42 p.m.