Triple
T33029320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Client-to-Client |
E845120
|
entity |
| Predicate | typicalTransportProtocol |
—
|
GENERATED |
| Object | TCP |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTransportProtocol Context triple: [Direct Client-to-Client, typicalTransportProtocol, TCP]
-
A.
transportProtocol
chosen
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
typicalNetTransport
Indicates the usual or most common means by which something is transported or carried from one place to another.
-
C.
intendedTransport
Indicates that one entity is meant or planned to be used as the means of transporting another entity.
-
D.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
E.
protocolName
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:24 a.m.