Triple
T8471108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonjour |
E200281
|
entity |
| Predicate | implementsStandard |
P1587
|
FINISHED |
| Object |
RFC 6763
RFC 6763 is the Internet standard that defines DNS-Based Service Discovery (DNS-SD), a mechanism for discovering network services using DNS queries.
|
E736564
|
NE FINISHED |
How this triple was built (4 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: RFC 6763 | Statement: [Bonjour, implementsStandard, RFC 6763]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6763 Context triple: [Bonjour, implementsStandard, RFC 6763]
-
A.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
B.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 6763 Triple: [Bonjour, implementsStandard, RFC 6763]
Generated description
RFC 6763 is the Internet standard that defines DNS-Based Service Discovery (DNS-SD), a mechanism for discovering network services using DNS queries.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6763 Target entity description: RFC 6763 is the Internet standard that defines DNS-Based Service Discovery (DNS-SD), a mechanism for discovering network services using DNS queries.
-
A.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
B.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- F. None of above. chosen
Provenance (5 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39fc9bf481908e37919b13465d18 |
completed | April 2, 2026, 9:42 a.m. |
| NEDg | Description generation | batch_69ce3b1e188c8190ad894478141f6501 |
completed | April 2, 2026, 9:47 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce3bfd00948190b3956be3f8c5d547 |
completed | April 2, 2026, 9:50 a.m. |
Created at: March 30, 2026, 6:11 p.m.