Triple
T1077172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAT64 |
E23865
|
entity |
| Predicate | relatedRFC |
P9936
|
FINISHED |
| Object |
RFC 6145
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
|
E129973
|
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 6145 | Statement: [NAT64, relatedRFC, RFC 6145]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6145 Context triple: [NAT64, relatedRFC, RFC 6145]
-
A.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
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.
-
E.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
- 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 6145 Triple: [NAT64, relatedRFC, RFC 6145]
Generated description
RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6145 Target entity description: RFC 6145 is an IETF standard that specifies the stateless translation mechanism between IPv4 and IPv6 packet headers used in NAT64 environments.
-
A.
RFC 6146
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
B.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
C.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
D.
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.
-
E.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac599e543c8190bbb0558379d8d9d5 |
completed | March 7, 2026, 5 p.m. |
| NEDg | Description generation | batch_69ac5a1fd5448190a72354c1017dfcf4 |
completed | March 7, 2026, 5:02 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ac5a76e99c8190be49b80e31088693 |
completed | March 7, 2026, 5:03 p.m. |
Created at: March 1, 2026, 7:42 p.m.