Triple
T27735366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Net.Sockets.UdpClient |
E697515
|
entity |
| Predicate | defaultAddressFamily |
P2546
|
FINISHED |
| Object | InterNetwork |
—
|
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: InterNetwork | Statement: [System.Net.Sockets.UdpClient, defaultAddressFamily, InterNetwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultAddressFamily Context triple: [System.Net.Sockets.UdpClient, defaultAddressFamily, InterNetwork]
-
A.
addressFamily
chosen
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
-
B.
socketFamily
Indicates the type of communication protocol family (e.g., IPv4, IPv6, Unix domain) that a socket belongs to.
-
C.
protocolFamily
Indicates that one protocol belongs to, or is categorized under, a broader protocol family or group.
-
D.
networkFamily
Indicates a relationship where entities belong to the same network grouping or family, typically sharing common infrastructure, protocols, or organizational affiliation.
-
E.
typicalDestinationAddress
Indicates the address that is most commonly or usually used as the destination for something or someone.
- 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_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 3:12 p.m.