Triple
T7928696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8999 |
E184130
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 9000 |
E48577
|
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 9000 | Statement: [RFC 8999, relatedTo, RFC 9000]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9000 Context triple: [RFC 8999, relatedTo, RFC 9000]
-
A.
RFC 9000
chosen
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.
-
B.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
C.
RFC 9250
RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
-
D.
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.
-
E.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c01602081908ea1af24785260ff |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:07 p.m.