Triple
T38237140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Transmission Selection |
E1013651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bandwidth allocation algorithm |
C19811
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: bandwidth allocation algorithm Context triple: [Enhanced Transmission Selection, instanceOf, bandwidth allocation algorithm]
-
A.
active queue management algorithm
An active queue management algorithm is a network mechanism that proactively controls packet queues by selectively dropping or marking packets before buffers overflow to reduce congestion, latency, and packet loss.
-
B.
load-balancing algorithm
A load-balancing algorithm is a method for distributing incoming work or network traffic across multiple resources (such as servers or processors) to optimize performance, maximize throughput, and ensure reliability.
-
C.
Explicit Congestion Notification mechanism
An Explicit Congestion Notification mechanism is a network feature that allows routers to signal impending congestion to endpoints by marking packets instead of dropping them, enabling proactive congestion control and improved performance.
-
D.
network protocol algorithm
A network protocol algorithm is a defined set of rules and procedures that govern how data is formatted, transmitted, routed, and received across interconnected devices in a communication network.
-
E.
media access control technique
chosen
A media access control technique is a method or protocol that governs how multiple devices share and coordinate access to a common communication medium to avoid collisions and ensure efficient data transmission.
- F. None of above.
Provenance (1 batch)
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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.