Triple
T380436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHATWG |
E8665
|
entity |
| Predicate | maintains |
P1580
|
FINISHED |
| Object |
URL Standard
The URL Standard is a technical specification by the WHATWG that defines how URLs are parsed, processed, and handled consistently across web browsers and platforms.
|
E49006
|
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: URL Standard | Statement: [WHATWG, maintains, URL Standard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: URL Standard Context triple: [WHATWG, maintains, URL Standard]
-
A.
HTTPS
HTTPS is the secure version of the HTTP protocol that encrypts data exchanged between a client and server to protect confidentiality and integrity on the web.
-
B.
Internet Standard
An Internet Standard is a formal, widely implemented and stable technical specification approved by the Internet Engineering Task Force (IETF) as part of the core protocols and practices that define how the Internet operates.
-
C.
Fetch Standard
The Fetch Standard is a web platform specification that defines a modern, unified API and processing model for fetching resources (such as HTTP requests and responses) across browsers and other environments.
-
D.
Encoding Standard
The Encoding Standard is a WHATWG specification that defines how text is encoded and decoded on the web to ensure consistent character handling across browsers and platforms.
-
E.
RFC 2818
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
- 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: URL Standard Triple: [WHATWG, maintains, URL Standard]
Generated description
The URL Standard is a technical specification by the WHATWG that defines how URLs are parsed, processed, and handled consistently across web browsers and platforms.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: URL Standard Target entity description: The URL Standard is a technical specification by the WHATWG that defines how URLs are parsed, processed, and handled consistently across web browsers and platforms.
-
A.
HTTPS
HTTPS is the secure version of the HTTP protocol that encrypts data exchanged between a client and server to protect confidentiality and integrity on the web.
-
B.
Internet Standard
An Internet Standard is a formal, widely implemented and stable technical specification approved by the Internet Engineering Task Force (IETF) as part of the core protocols and practices that define how the Internet operates.
-
C.
Fetch Standard
The Fetch Standard is a web platform specification that defines a modern, unified API and processing model for fetching resources (such as HTTP requests and responses) across browsers and other environments.
-
D.
Encoding Standard
The Encoding Standard is a WHATWG specification that defines how text is encoded and decoded on the web to ensure consistent character handling across browsers and platforms.
-
E.
RFC 2818
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
- F. None of above. chosen
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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2c95088190a603bb1ee076ebd6 |
completed | Feb. 28, 2026, 1:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3fe92911881908ee7f88d5c628ec9 |
completed | March 1, 2026, 8:53 a.m. |
| NEDg | Description generation | batch_69a3ff327d1c81909cbbbfd53fc74559 |
completed | March 1, 2026, 8:56 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a40101f7e4819099bd776c79b4d8cc |
completed | March 1, 2026, 9:04 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.