Triple
T10560213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | draft-ietf-quic-recovery |
E249196
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | RFC 9002 |
E50020
|
NE FINISHED |
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 9002 | Statement: [draft-ietf-quic-recovery, successor, RFC 9002]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9002 Context triple: [draft-ietf-quic-recovery, successor, RFC 9002]
-
A.
RFC 9002
chosen
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
B.
RFC 9204
RFC 9204 is the IETF standard that defines QPACK, the header compression mechanism used by the HTTP/3 protocol.
-
C.
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.
-
D.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
E.
RFC 9293
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271f3c6c819080b49fbe3aa09e09 |
completed | April 7, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94b38b4c081908cc2816144c23152 |
completed | April 10, 2026, 7:10 p.m. |
Created at: April 6, 2026, 12:35 p.m.