Triple
T16808133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tab Atkins Jr. |
E408530
|
entity |
| Predicate | affiliation |
P10
|
FINISHED |
| Object | Web Hypertext Application Technology Working Group |
E48499
|
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: Web Hypertext Application Technology Working Group | Statement: [Tab Atkins Jr., affiliation, Web Hypertext Application Technology Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Web Hypertext Application Technology Working Group Context triple: [Tab Atkins Jr., affiliation, Web Hypertext Application Technology Working Group]
-
A.
Web Hypertext Application Technology Working Group
chosen
The Web Hypertext Application Technology Working Group (WHATWG) is a community of browser vendors, web developers, and other stakeholders that collaboratively develops and maintains key web standards, including the HTML Living Standard.
-
B.
Web Applications Working Group
The Web Applications Working Group is a W3C standards body responsible for developing and maintaining core web platform APIs and specifications that enable rich, interactive web applications.
-
C.
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.
-
D.
W3C Technical Architecture Group
The W3C Technical Architecture Group is a specialized body within the World Wide Web Consortium that steers the evolution of web architecture and ensures the consistency and integrity of web standards.
-
E.
W3C Web Application technologies
W3C Web Application technologies are a suite of open web standards and APIs defined by the World Wide Web Consortium to enable rich, interoperable, and secure web applications across platforms and devices.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cde590819080dc474292b023ee |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b28f125481909664363904f4c031 |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:22 a.m.