Triple
T27735401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Net.Sockets.UdpClient |
E697515
|
entity |
| Predicate | supportsBroadcast |
P31727
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [System.Net.Sockets.UdpClient, supportsBroadcast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBroadcast Context triple: [System.Net.Sockets.UdpClient, supportsBroadcast, true]
-
A.
hasBroadcastFeature
chosen
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
B.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
C.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
-
D.
supportsAdvertising
Indicates that one entity enables, allows, or is compatible with the display or delivery of advertising for another entity.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: April 27, 2026, 3:12 p.m.