Triple
T20638686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 200GBASE-R PHYs |
E507157
|
entity |
| Predicate | transmissionDirection |
P140870
|
FINISHED |
| Object | bidirectional full duplex |
—
|
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: bidirectional full duplex | Statement: [200GBASE-R PHYs, transmissionDirection, bidirectional full duplex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionDirection Context triple: [200GBASE-R PHYs, transmissionDirection, bidirectional full duplex]
-
A.
connectionDirection
Indicates the directional flow or orientation of a connection from one entity to another.
-
B.
netTransportDirection
Indicates the overall direction in which something (such as material, energy, or information) is being transported when considering all contributing flows together.
-
C.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
D.
packetDirection
Indicates the direction in which a data packet is traveling between network endpoints (e.g., inbound or outbound).
-
E.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad1163008190aa9df36750a952d2 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.