Triple
T271035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best Current Practice |
E5632
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Request for Comments |
E5627
|
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: Request for Comments | Statement: [Best Current Practice, relatedTo, Request for Comments]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Request for Comments Context triple: [Best Current Practice, relatedTo, Request for Comments]
-
A.
RFCs
chosen
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.
-
B.
RFC Editor
The RFC Editor is the organization responsible for editing, publishing, and maintaining the Request for Comments (RFC) series that documents standards and technical notes for the Internet community.
-
C.
CFP
CFP is the postseason tournament system used to determine the national champion of NCAA Division I FBS college football in the United States.
-
D.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- 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_69a3949fbdd48190847ef6d7decdc61e |
completed | March 1, 2026, 1:21 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.