Triple
T10104322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Content-Range header field |
E216279
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | Hypertext Transfer Protocol (HTTP/1.1): Range Requests |
E220182
|
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: Hypertext Transfer Protocol (HTTP/1.1): Range Requests | Statement: [Content-Range header field, definedIn, Hypertext Transfer Protocol (HTTP/1.1): Range Requests]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hypertext Transfer Protocol (HTTP/1.1): Range Requests Context triple: [Content-Range header field, definedIn, Hypertext Transfer Protocol (HTTP/1.1): Range Requests]
-
A.
HTTP/1.1 Range Requests
chosen
HTTP/1.1 Range Requests is the HTTP mechanism that allows clients to request and receive only specific portions (byte ranges) of a resource, enabling efficient partial downloads and resumable transfers.
-
B.
Content-Range header field
The Content-Range header field is an HTTP response header used to indicate the specific byte range of a resource being returned, typically in support of partial content delivery and resumable downloads.
-
C.
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.
-
D.
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.
-
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.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09c961081909848acec4438c300 |
completed | April 2, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cbf9ffb88190a87833d6fe080950 |
completed | April 5, 2026, 8:54 p.m. |
Created at: March 30, 2026, 9:03 p.m.