Triple
T29392036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPI |
E745388
|
entity |
| Predicate | signalRole_MISO |
P85083
|
FINISHED |
| Object | master in slave out data line |
—
|
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: master in slave out data line | Statement: [SPI, signalRole_MISO, master in slave out data line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalRole_MISO Context triple: [SPI, signalRole_MISO, master in slave out data line]
-
A.
signalRole_MOSI
Indicates that one entity functions as a signal or communication role specifically associated with the MOSI (Master Out Slave In) line in a signaling or communication context.
-
B.
hasSerialInputPin
chosen
Indicates that an entity possesses a pin or connector specifically designated for receiving serial input signals.
-
C.
serialInterface
Indicates a relationship where data is transmitted between components over a serial communication interface (one bit at a time over a communication line or bus).
-
D.
signalGroundPins
Indicates that certain pins serve as ground reference connections for signal-carrying pins in an electrical or electronic interface.
-
E.
bitSerialOrParallel
Indicates whether a bit-level operation or data transfer is performed in serial form (one bit at a time) or in parallel form (multiple bits simultaneously).
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 2:43 p.m.