Triple
T21190941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1883 |
E522208
|
entity |
| Predicate | definesConcept |
P773
|
FINISHED |
| Object | IPv6 extension headers |
—
|
NE NERFINISHED |
How this triple was built (3 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: IPv6 extension headers | Statement: [RFC 1883, definesConcept, IPv6 extension headers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IPv6 extension headers Context triple: [RFC 1883, definesConcept, IPv6 extension headers]
-
A.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
B.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
C.
TCP/IP header compression
TCP/IP header compression is a technique that significantly reduces the size of TCP/IP packet headers to improve performance over low-bandwidth or high-latency network links.
-
D.
Transport Layer Security (TLS) Extensions: Extension Definitions
"Transport Layer Security (TLS) Extensions: Extension Definitions" is an IETF standards document (RFC 6066) that specifies a set of protocol extensions enhancing the flexibility and capabilities of TLS, such as server name indication and session ticket mechanisms.
-
E.
IP/ICMP Translation Algorithm
IP/ICMP Translation Algorithm is an IETF-specified mechanism that enables interoperability between IPv4 and IPv6 networks by translating IP and ICMP headers and messages between the two protocol versions.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IPv6 extension headers Target entity description: IPv6 extension headers are optional, chained header fields in IPv6 packets that provide additional functionality such as routing, fragmentation, security, and quality-of-service beyond the basic IPv6 header.
-
A.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
B.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
C.
TCP/IP header compression
TCP/IP header compression is a technique that significantly reduces the size of TCP/IP packet headers to improve performance over low-bandwidth or high-latency network links.
-
D.
Transport Layer Security (TLS) Extensions: Extension Definitions
"Transport Layer Security (TLS) Extensions: Extension Definitions" is an IETF standards document (RFC 6066) that specifies a set of protocol extensions enhancing the flexibility and capabilities of TLS, such as server name indication and session ticket mechanisms.
-
E.
IP/ICMP Translation Algorithm
IP/ICMP Translation Algorithm is an IETF-specified mechanism that enables interoperability between IPv4 and IPv6 networks by translating IP and ICMP headers and messages between the two protocol versions.
- F. None of above. chosen
Provenance (2 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.