Triple
T29392034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPI |
E745388
|
entity |
| Predicate | signalRole_SCLK |
P4618
|
FINISHED |
| Object | serial clock from master |
—
|
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: serial clock from master | Statement: [SPI, signalRole_SCLK, serial clock from master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalRole_SCLK Context triple: [SPI, signalRole_SCLK, serial clock from master]
-
A.
hasClockInput
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
B.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
C.
controlSignals
Indicates that one entity sends or governs directive signals that determine or influence the behavior or operation of another entity.
-
D.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
E.
clockRecovery
Indicates the process or relationship by which a receiver reconstructs or synchronizes its clock signal from an incoming data stream or signal.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:43 p.m.