Triple
T18564608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3490 |
E453730
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 5892 |
—
|
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 5892 | Statement: [RFC 3490, obsoletedBy, RFC 5892]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5892 Context triple: [RFC 3490, obsoletedBy, RFC 5892]
-
A.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
B.
RFC 5072
RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
-
C.
RFC 5891
RFC 5891 is an Internet standard that defines the protocol requirements and processing rules for Internationalized Domain Names (IDNs) in applications as part of the IDNA2008 framework.
-
D.
RFC 5890
RFC 5890 is an Internet Engineering Task Force (IETF) standard that defines the terminology and concepts for Internationalized Domain Names (IDNs) in the Domain Name System (DNS).
-
E.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
- 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 5892 Target entity description: RFC 5892 is an IETF standard that defines the rules for allowable Unicode code points in Internationalized Domain Names (IDNs) under the IDNA2008 framework.
-
A.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
B.
RFC 5072
RFC 5072 is an Internet Engineering Task Force (IETF) standard that specifies how IPv6 packets are transmitted over Point-to-Point Protocol (PPP) links.
-
C.
RFC 5891
RFC 5891 is an Internet standard that defines the protocol requirements and processing rules for Internationalized Domain Names (IDNs) in applications as part of the IDNA2008 framework.
-
D.
RFC 5890
RFC 5890 is an Internet Engineering Task Force (IETF) standard that defines the terminology and concepts for Internationalized Domain Names (IDNs) in the Domain Name System (DNS).
-
E.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
Created at: April 10, 2026, 11:42 a.m.