Triple
T8472651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centronics parallel port |
E200314
|
entity |
| Predicate | handshakingSignals |
P82794
|
FINISHED |
| Object | STROBE |
—
|
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: STROBE | Statement: [Centronics parallel port, handshakingSignals, STROBE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handshakingSignals Context triple: [Centronics parallel port, handshakingSignals, STROBE]
-
A.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
B.
handshakeRole
Indicates the specific part or function an entity assumes in a handshake interaction between participants.
-
C.
compatibleWithSignaling
Indicates that one entity can correctly interpret, process, or operate using the signaling mechanisms, protocols, or formats employed by another entity.
-
D.
usesBalancedSignaling
Indicates that an entity employs a signaling strategy in which opposing or complementary signals are used in a coordinated, proportionate way to maintain balance in communication or control.
-
E.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:11 p.m.