Triple
T21091499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 761 |
E519648
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 9293 |
—
|
NE NERFINISHED |
How this triple was built (2 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 9293 | Statement: [RFC 761, obsoletedBy, RFC 9293]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9293 Context triple: [RFC 761, obsoletedBy, RFC 9293]
-
A.
RFC 9293
chosen
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
B.
RFC 9589
RFC 9589 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the Network Time Protocol version 4 (NTPv4) specification to address modern requirements and improvements in time synchronization.
-
C.
RFC 9204
RFC 9204 is the IETF standard that defines QPACK, the header compression mechanism used by the HTTP/3 protocol.
-
D.
RFC 9082
RFC 9082 is an IETF standard that specifies the HTTP-based query format and response structure for the Registration Data Access Protocol (RDAP), used to access domain name and Internet number registration data.
-
E.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:51 p.m.