Triple
T21191380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5996 |
E522218
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 4306 |
—
|
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: RFC 4306 | Statement: [RFC 5996, obsoletes, RFC 4306]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4306 Context triple: [RFC 5996, obsoletes, RFC 4306]
-
A.
RFC 3406
RFC 3406 is an IETF document that specifies the procedures and requirements for registering Uniform Resource Name (URN) namespaces.
-
B.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
C.
RFC 4366
RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
-
D.
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.
-
E.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
- 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: RFC 4306 Target entity description: RFC 4306 is the original specification of the Internet Key Exchange Protocol version 2 (IKEv2), defining mechanisms for setting up secure IPsec-based VPN connections.
-
A.
RFC 3406
RFC 3406 is an IETF document that specifies the procedures and requirements for registering Uniform Resource Name (URN) namespaces.
-
B.
RFC 4633
RFC 4633 is an Internet Engineering Task Force (IETF) standard that updates and refines the Classless Inter-Domain Routing (CIDR) architecture for IP addressing and routing.
-
C.
RFC 4366
RFC 4366 is an earlier IETF specification that extended TLS with additional client and server features, later superseded and refined by RFC 6066.
-
D.
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.
-
E.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
- 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_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.