Triple
T10447587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building Protocols with HTTP |
E246333
|
entity |
| Predicate | rfcNumber |
P26175
|
FINISHED |
| Object | RFC 9205 |
E48181
|
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 9205 | Statement: [Building Protocols with HTTP, rfcNumber, RFC 9205]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9205 Context triple: [Building Protocols with HTTP, rfcNumber, RFC 9205]
-
A.
RFC 9205
chosen
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
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.
-
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 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 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.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fdc10c8081908a3801fe1dea63de |
completed | April 7, 2026, 12:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87ef4e0dc81908d7cf0f2b6f4cd98 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 6, 2026, 12:16 p.m.