Triple
T21802408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2793 |
—
|
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 2793 | Statement: [RFC 4632, obsoletes, RFC 2793]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2793 Context triple: [RFC 4632, obsoletes, RFC 2793]
-
A.
RFC 3629
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
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.
-
D.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
E.
RFC 2829
RFC 2829 is an earlier IETF standard that specified authentication methods and security mechanisms for LDAPv3 directory access before being superseded by later updates.
- 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 2793 Target entity description: RFC 2793 is an older Internet Engineering Task Force (IETF) specification that defined an early standard related to IP networking, later superseded by RFC 4632.
-
A.
RFC 3629
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
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.
-
D.
RFC 3996
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
E.
RFC 2829
RFC 2829 is an earlier IETF standard that specified authentication methods and security mechanisms for LDAPv3 directory access before being superseded by later updates.
- 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.