Triple
T2703270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2068 |
E59281
|
entity |
| Predicate | definesHeaderField |
P3703
|
FINISHED |
| Object |
Accept-Charset
Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
|
E290850
|
NE FINISHED |
How this triple was built (4 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: Accept-Charset | Statement: [RFC 2068, definesHeaderField, Accept-Charset]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Accept-Charset Context triple: [RFC 2068, definesHeaderField, Accept-Charset]
-
A.
Accept-Encoding
Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
-
B.
Accept-Language
Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
-
C.
UTF-8
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
D.
ASCII
ASCII is a widely used character encoding standard that represents text in computers and other devices using 7-bit numerical codes for letters, digits, punctuation, and control characters.
-
E.
Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Accept-Charset Triple: [RFC 2068, definesHeaderField, Accept-Charset]
Generated description
Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Accept-Charset Target entity description: Accept-Charset is an HTTP request header that tells the server which character encodings the client is able to understand and prefers.
-
A.
Accept-Encoding
Accept-Encoding is an HTTP request header that tells the server which content-encoding algorithms (like gzip or deflate) the client can handle so the server can choose an appropriate compression method.
-
B.
Accept-Language
Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
-
C.
UTF-8
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
D.
ASCII
ASCII is a widely used character encoding standard that represents text in computers and other devices using 7-bit numerical codes for letters, digits, punctuation, and control characters.
-
E.
Content-Encoding
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
- F. None of above. chosen
Provenance (5 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda5011bc8190ae4e41da391e759c |
completed | March 7, 2026, 7:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afaf76caec8190930ead7931f7ea91 |
completed | March 10, 2026, 5:43 a.m. |
| NEDg | Description generation | batch_69afb01c248c81909af7358da96aa588 |
completed | March 10, 2026, 5:46 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afb0ae71888190ab0675b7897f1589 |
completed | March 10, 2026, 5:48 a.m. |
Created at: March 6, 2026, 9:55 p.m.