Triple
T515902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transmission Control Protocol |
E10705
|
entity |
| Predicate | congestionControlAlgorithm |
P15302
|
FINISHED |
| Object | slow start |
—
|
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: slow start | Statement: [Transmission Control Protocol, congestionControlAlgorithm, slow start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congestionControlAlgorithm Context triple: [Transmission Control Protocol, congestionControlAlgorithm, slow start]
-
A.
headerCompressionAlgorithm
Indicates the algorithm used to compress the header portion of a data structure or message.
-
B.
flowControl
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
-
C.
overheadComparedToTCP
Indicates the additional protocol or processing cost incurred by something relative to using TCP as the baseline.
-
D.
convergenceProperty
Indicates that one entity has a convergence-related characteristic or behavior with respect to another entity, such as approaching a limit or stabilizing under repeated application.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1836b688190a60cc901a8724159 |
completed | Feb. 28, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f1137e948190838303cdaa757a5a |
completed | Feb. 28, 2026, 1:43 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.