Triple
T1881512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 9110 |
E39861
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object |
HTTP core specification set
The HTTP core specification set is the collection of foundational IETF standards that define the semantics, messaging, and core mechanisms of the Hypertext Transfer Protocol used on the web.
|
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: HTTP core specification set | Statement: [RFC 9110, partOf, HTTP core specification set]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP core specification set Context triple: [RFC 9110, partOf, HTTP core specification set]
-
A.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
C.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
D.
HTTP/1.1
HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
-
E.
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.
- 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: HTTP core specification set Triple: [RFC 9110, partOf, HTTP core specification set]
Generated description
The HTTP core specification set is the collection of foundational IETF standards that define the semantics, messaging, and core mechanisms of the Hypertext Transfer Protocol used on the web.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: HTTP core specification set Target entity description: The HTTP core specification set is the collection of foundational IETF standards that define the semantics, messaging, and core mechanisms of the Hypertext Transfer Protocol used on the web.
-
A.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
C.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
D.
HTTP/1.1
HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
-
E.
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.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0fb95b48190af5286662c8b9734 |
completed | March 7, 2026, 5 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf5c55e081909fc6912e1283a73a |
completed | March 8, 2026, 8:43 p.m. |
| NEDg | Description generation | batch_69ade089c3848190a730957799b08993 |
completed | March 8, 2026, 8:48 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ade14bd7e48190bf7d4832a4d46992 |
completed | March 8, 2026, 8:51 p.m. |
Created at: March 4, 2026, 7:34 p.m.