Triple
T270465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DHCP |
E5621
|
entity |
| Predicate | usesTransportProtocol |
P3331
|
FINISHED |
| Object | UDP |
—
|
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: UDP | Statement: [DHCP, usesTransportProtocol, UDP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTransportProtocol Context triple: [DHCP, usesTransportProtocol, UDP]
-
A.
usesProtocolSuite
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
B.
usedInProtocol
chosen
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
C.
hasTransportAuthority
Indicates that one entity holds official power or responsibility to manage, regulate, or oversee transportation services or infrastructure for another entity or area.
-
D.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
E.
hasTransportationSystem
Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.