Triple
T63744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDP |
E1266
|
entity |
| Predicate | overheadComparedToTCP |
P3693
|
FINISHED |
| Object | lower overhead |
—
|
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: lower overhead | Statement: [UDP, overheadComparedToTCP, lower overhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overheadComparedToTCP Context triple: [UDP, overheadComparedToTCP, lower overhead]
-
A.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
dateOfTCPIPTransition
Indicates the date on which an entity transitioned its networking or communication systems to use the TCP/IP protocol.
-
E.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.