Triple
T21802379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2764 |
—
|
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 2764 | Statement: [RFC 4632, obsoletes, RFC 2764]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2764 Context triple: [RFC 4632, obsoletes, RFC 2764]
-
A.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
B.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
C.
RFC 2763
RFC 2763 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for classless inter-domain routing (CIDR) address allocation and aggregation before being superseded by RFC 4632.
-
D.
RFC 2760
RFC 2760 is an Internet Engineering Task Force (IETF) document that provided guidelines and considerations for the deployment and operation of Classless Inter-Domain Routing (CIDR) on the Internet.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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 2764 Target entity description: RFC 2764 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for virtual private networks (VPNs) before being superseded by later standards.
-
A.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
B.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
C.
RFC 2763
RFC 2763 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for classless inter-domain routing (CIDR) address allocation and aggregation before being superseded by RFC 4632.
-
D.
RFC 2760
RFC 2760 is an Internet Engineering Task Force (IETF) document that provided guidelines and considerations for the deployment and operation of Classless Inter-Domain Routing (CIDR) on the Internet.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
Created at: April 16, 2026, 6:53 p.m.