Triple
T29392035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPI |
E745388
|
entity |
| Predicate | signalRole_MOSI |
P168146
|
FINISHED |
| Object | master out slave in 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 out slave in data line | Statement: [SPI, signalRole_MOSI, master out slave in data line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalRole_MOSI Context triple: [SPI, signalRole_MOSI, master out slave in data line]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
C.
signalPolarity
Indicates the directional orientation or sign (positive or negative) of a signal relative to a defined reference.
-
D.
controlSignals
Indicates that one entity sends or governs directive signals that determine or influence the behavior or operation of another entity.
-
E.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
- 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_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 2:43 p.m.