Triple
T2742865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7234 |
E60792
|
entity |
| Predicate | isPartOf |
P10
|
FINISHED |
| Object |
RFC 7230–RFC 7235 HTTP/1.1 core specifications
The RFC 7230–RFC 7235 HTTP/1.1 core specifications are a set of IETF standards that collectively define the fundamental semantics, message syntax, and operational behavior of the HTTP/1.1 protocol.
|
E42395
|
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: RFC 7230–RFC 7235 HTTP/1.1 core specifications | Statement: [RFC 7234, isPartOf, RFC 7230–RFC 7235 HTTP/1.1 core specifications]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7230–RFC 7235 HTTP/1.1 core specifications Context triple: [RFC 7234, isPartOf, RFC 7230–RFC 7235 HTTP/1.1 core specifications]
-
A.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
B.
RFC 2616
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
-
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 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
- 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: RFC 7230–RFC 7235 HTTP/1.1 core specifications Triple: [RFC 7234, isPartOf, RFC 7230–RFC 7235 HTTP/1.1 core specifications]
Generated description
The RFC 7230–RFC 7235 HTTP/1.1 core specifications are a set of IETF standards that collectively define the fundamental semantics, message syntax, and operational behavior of the HTTP/1.1 protocol.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 7230–RFC 7235 HTTP/1.1 core specifications Target entity description: The RFC 7230–RFC 7235 HTTP/1.1 core specifications are a set of IETF standards that collectively define the fundamental semantics, message syntax, and operational behavior of the HTTP/1.1 protocol.
-
A.
RFC 7230
chosen
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
B.
RFC 2616
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
-
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 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
- F. None of above.
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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb314410819095d4822f9277e6ff |
completed | March 7, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afbbcca19881908b2e2eb0478c3e45 |
completed | March 10, 2026, 6:35 a.m. |
| NEDg | Description generation | batch_69afbc758cc48190a96f80a850316ce3 |
completed | March 10, 2026, 6:38 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afbd7be9088190a19bed27249e95c4 |
completed | March 10, 2026, 6:43 a.m. |
Created at: March 6, 2026, 9:56 p.m.