Triple
T22814835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF RFC 8826 |
E565070
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | IETF RFC 8827 |
—
|
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: IETF RFC 8827 | Statement: [IETF RFC 8826, obsoletes, IETF RFC 8827]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF RFC 8827 Context triple: [IETF RFC 8826, obsoletes, IETF RFC 8827]
-
A.
RFC 8927
RFC 8927 is an IETF specification that defines how to use JSON Schema for describing and validating YANG data models in network management.
-
B.
IETF RFC 8826
IETF RFC 8826 is a standards document that specifies the security considerations and requirements for real-time communication using WebRTC.
-
C.
IETF RFC 8825
IETF RFC 8825 is a standards document that specifies the overall architecture, signaling, and media handling framework for WebRTC real-time communication over IP networks.
-
D.
RFC 2787
RFC 2787 is an Internet Engineering Task Force (IETF) document that originally specified a now-superseded networking standard or protocol later replaced by RFC 4632.
-
E.
RFC 7482
RFC 7482 is the IETF specification that defines the HTTP-based query format and usage for the Registration Data Access Protocol (RDAP).
- 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: IETF RFC 8827 Target entity description: IETF RFC 8827 is an Internet Engineering Task Force standard that defines updated specifications related to real-time communication security and media handling, later superseded by RFC 8826.
-
A.
RFC 8927
RFC 8927 is an IETF specification that defines how to use JSON Schema for describing and validating YANG data models in network management.
-
B.
IETF RFC 8826
IETF RFC 8826 is a standards document that specifies the security considerations and requirements for real-time communication using WebRTC.
-
C.
IETF RFC 8825
IETF RFC 8825 is a standards document that specifies the overall architecture, signaling, and media handling framework for WebRTC real-time communication over IP networks.
-
D.
RFC 2787
RFC 2787 is an Internet Engineering Task Force (IETF) document that originally specified a now-superseded networking standard or protocol later replaced by RFC 4632.
-
E.
RFC 7482
RFC 7482 is the IETF specification that defines the HTTP-based query format and usage for the Registration Data Access Protocol (RDAP).
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
Created at: April 17, 2026, 3:33 p.m.