Triple
T2187948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Working Group |
E49793
|
entity |
| Predicate | responsibleFor |
P636
|
FINISHED |
| Object | HTTP/1.1 authentication specification |
E41246
|
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: HTTP/1.1 authentication specification | Statement: [HTTP Working Group, responsibleFor, HTTP/1.1 authentication specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP/1.1 authentication specification Context triple: [HTTP Working Group, responsibleFor, HTTP/1.1 authentication specification]
-
A.
RFC 2617
RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
-
B.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
C.
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.
-
D.
RFC 7235
chosen
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.
-
E.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf130ef081908adb4a22f056be5b |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5dada268819082ddc4acd58e19f3 |
completed | March 9, 2026, 5:42 a.m. |
Created at: March 4, 2026, 7:45 p.m.