Triple
T28836337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytime Protocol |
E728193
|
entity |
| Predicate | reliabilityWithUDP |
P3692
|
FINISHED |
| Object | unreliable, best-effort delivery |
—
|
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: unreliable, best-effort delivery | Statement: [Daytime Protocol, reliabilityWithUDP, unreliable, best-effort delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliabilityWithUDP Context triple: [Daytime Protocol, reliabilityWithUDP, unreliable, best-effort delivery]
-
A.
reliabilityComparedToTCP
chosen
Indicates how the reliability of one protocol or mechanism compares relative to that of TCP.
-
B.
isUnreliableTransportAware
Indicates that an entity recognizes and accounts for the possibility that the underlying transport mechanism may be unreliable (e.g., subject to message loss, delay, or reordering) when performing its operations.
-
C.
reliabilityRecord
Indicates that there exists a record or documentation capturing the reliability characteristics, performance, or history associated with an entity or relationship.
-
D.
reliabilityHigherThan
Indicates that one entity is considered to have greater reliability than another entity.
-
E.
differenceFromUDP
Indicates a relationship where something is characterized or measured in terms of how it differs from UDP (User Datagram Protocol) in behavior, properties, or implementation.
- F. None of above.
Provenance (3 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:39 a.m.