Triple
T1817402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7232 |
E40465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTTP/1.1 specification |
C902
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: HTTP/1.1 specification Context triple: [RFC 7232, instanceOf, HTTP/1.1 specification]
-
A.
W3C specification
A W3C specification is an official, collaboratively developed technical standard published by the World Wide Web Consortium that defines interoperable protocols, formats, and best practices for the World Wide Web.
-
B.
DNS specification
A DNS specification defines the formal rules, data structures, and protocols governing how domain names are translated into IP addresses and other resource records across the internet.
-
C.
web protocol
chosen
A web protocol is a standardized set of rules and formats that govern how data is requested, transmitted, and received between clients and servers over the World Wide Web.
-
D.
W3C technical specification
A W3C technical specification is a formal, consensus-based document published by the World Wide Web Consortium that defines standards, protocols, and guidelines to ensure the interoperability and evolution of the World Wide Web.
-
E.
W3C specification maturity level
The W3C specification maturity level represents the formal stage in the World Wide Web Consortium’s standardization process that indicates how stable, reviewed, and implementation-ready a web technology specification is.
- F. None of above.
Provenance (1 batch)
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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.