Triple
T270803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC |
E5627
|
entity |
| Predicate | includesType |
P121
|
FINISHED |
| Object | Best Current Practice RFC |
E5632
|
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: Best Current Practice RFC | Statement: [RFC, includesType, Best Current Practice RFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Best Current Practice RFC Context triple: [RFC, includesType, Best Current Practice RFC]
-
A.
Best Current Practice
chosen
Best Current Practice is a series of IETF documents that record community consensus on recommended methods, procedures, and guidelines for using and managing Internet technologies.
-
B.
RFCs
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
C.
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.
-
D.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
E.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db17e8c8190a6ebcadd8a0abf4d |
completed | Feb. 28, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a38f51aeac81908c6d398e650dc315 |
completed | March 1, 2026, 12:58 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.