RFC 4180
E185669
RFC 4180 is the Internet standard that formally specifies the common format and rules for Comma-Separated Values (CSV) files.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Common Format and MIME Type for Comma-Separated Values (CSV) Files | 1 |
| RFC 4180 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1647757 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4180 Context triple: [CSV, definedIn, RFC 4180]
-
A.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
E.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4180 Target entity description: RFC 4180 is the Internet standard that formally specifies the common format and rules for Comma-Separated Values (CSV) files.
-
A.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
-
B.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
E.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
CSV specification
ⓘ
Internet standard ⓘ Request for Comments document ⓘ |
| aimsTo | improve interoperability of CSV files ⓘ |
| appliesTo |
CSV text data
ⓘ
Comma-Separated Values files ⓘ |
| category | Informational ⓘ |
| defines |
MIME type for CSV
ⓘ
common CSV file format ⓘ rules for CSV files ⓘ |
| definesFieldSeparator | comma ⓘ |
| definesFormatFor | tabular data in text form ⓘ |
| definesLineTerminator | CRLF ⓘ |
| definesMediaType | text/csv ⓘ |
| definesQuoteCharacter | double quote ⓘ |
| format | text ⓘ |
| intendedFor |
application implementers
ⓘ
protocol designers ⓘ software developers ⓘ |
| language | English ⓘ |
| partOfSeries | RFC series ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
CSV
ⓘ
Internet standards ⓘ MIME types ⓘ |
| rfcNumber | 4180 ⓘ |
| scope | text-based tabular data ⓘ |
| specifies |
CSV escaping of double quotes
ⓘ
CSV field delimiting rules ⓘ CSV handling of CRLF line endings ⓘ CSV handling of commas inside fields ⓘ CSV header row usage ⓘ CSV line break rules ⓘ CSV quoting rules ⓘ CSV record separation by CRLF ⓘ CSV record structure ⓘ text/csv MIME type ⓘ that all records should have the same number of fields ⓘ |
| standardizes | common CSV usage ⓘ |
| status | Informational RFC ⓘ |
| title |
RFC 4180
self-linksurface differs
ⓘ
surface form:
Common Format and MIME Type for Comma-Separated Values (CSV) Files
|
| usedFor |
data exchange
ⓘ
database data interchange ⓘ import and export of tabular data ⓘ spreadsheet data interchange ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 4180 Description of subject: RFC 4180 is the Internet standard that formally specifies the common format and rules for Comma-Separated Values (CSV) files.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.