Triple
T22109380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4787 |
E546374
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 7857 |
—
|
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 7857 | Statement: [RFC 4787, obsoletedBy, RFC 7857]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7857 Context triple: [RFC 4787, obsoletedBy, RFC 7857]
-
A.
RFC 7858
RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
-
B.
RFC 7218
RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
-
C.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
-
D.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
-
E.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
- 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 7857 Target entity description: RFC 7857 is an IETF standard that updates and refines behavioral requirements for network address translation (NAT) devices, particularly for unicast UDP traffic, superseding earlier NAT guidance.
-
A.
RFC 7858
RFC 7858 is the Internet standard that specifies how to secure DNS queries and responses using Transport Layer Security (TLS), commonly known as DNS over TLS.
-
B.
RFC 7218
RFC 7218 is an IETF standards document that specifies naming conventions and TLSA record usage guidelines for the DANE (DNS-Based Authentication of Named Entities) protocol.
-
C.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
-
D.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
-
E.
RFC 7127
RFC 7127 is an Internet Engineering Task Force (IETF) document that specifies procedures and guidelines related to the IETF standards process.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291b9c988190b3ddd06d1f40dc78 |
completed | April 28, 2026, 9:39 p.m. |
Created at: April 16, 2026, 8:30 p.m.