Triple
T22109377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4787 |
E546374
|
entity |
| Predicate | BCPNumber |
P34024
|
FINISHED |
| Object |
BCP 127
BCP 127 is a Best Current Practice document in the IETF that defines behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
|
E1518461
|
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: BCP 127 | Statement: [RFC 4787, BCPNumber, BCP 127]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 127 Context triple: [RFC 4787, BCPNumber, BCP 127]
-
A.
BCP 12
BCP 12 is a Best Current Practice document in the Internet standards process that provides guidance and recommendations related to the technical content of RFC 1908.
-
B.
BCP 175
BCP 175 is an IETF Best Current Practice document that defines procedures and policies for managing the DNS root zone’s trust anchor for DNSSEC.
-
C.
BCP 195
BCP 195 is an IETF Best Current Practice document that provides modern security recommendations for the use of Transport Layer Security (TLS) and Datagram TLS (DTLS) in Internet protocols.
-
D.
BCP 190
BCP 190 is a Best Current Practice document in the IETF standards series that provides guidance on the use and management of Uniform Resource Names (URNs).
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- 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: BCP 127 Triple: [RFC 4787, BCPNumber, BCP 127]
Generated description
BCP 127 is a Best Current Practice document in the IETF that defines behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: BCP 127 Target entity description: BCP 127 is a Best Current Practice document in the IETF that defines behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
A.
BCP 12
BCP 12 is a Best Current Practice document in the Internet standards process that provides guidance and recommendations related to the technical content of RFC 1908.
-
B.
BCP 175
BCP 175 is an IETF Best Current Practice document that defines procedures and policies for managing the DNS root zone’s trust anchor for DNSSEC.
-
C.
BCP 195
BCP 195 is an IETF Best Current Practice document that provides modern security recommendations for the use of Transport Layer Security (TLS) and Datagram TLS (DTLS) in Internet protocols.
-
D.
BCP 190
BCP 190 is a Best Current Practice document in the IETF standards series that provides guidance on the use and management of Uniform Resource Names (URNs).
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291b9c988190b3ddd06d1f40dc78 |
completed | April 28, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0a87ac12e881909ba2c0de6f3b26f5 |
completed | May 18, 2026, 3:29 a.m. |
| NEDg | Description generation | batch_6a0a88e654ac8190a0e77e946bd9722b |
completed | May 18, 2026, 3:35 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0a8966298c8190a0d0e7d2b6eacdb4 |
completed | May 18, 2026, 3:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.