Triple
T13636615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2481 |
E325863
|
entity |
| Predicate | updatesProtocolBehaviorOf |
P111404
|
FINISHED |
| Object | TCP congestion control |
—
|
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: TCP congestion control | Statement: [RFC 2481, updatesProtocolBehaviorOf, TCP congestion control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesProtocolBehaviorOf Context triple: [RFC 2481, updatesProtocolBehaviorOf, TCP congestion control]
-
A.
updateProtocol
Indicates that an entity modifies or revises an existing protocol, procedure, or set of rules to a newer or improved version.
-
B.
relatedToProtocolVersion
Indicates a relationship where something is associated with, governed by, or dependent on a specific protocol version.
-
C.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used by another entity.
-
D.
configurationProtocol
Indicates the protocol or method used to configure or set up a system, device, or component.
-
E.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc6043e148190a2a25f929cfa35e5 |
completed | April 12, 2026, 4:19 p.m. |
Created at: April 9, 2026, 9:51 p.m.