Triple
T10024772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2817 |
E200697
|
entity |
| Predicate | relatedWorkingGroup |
P85663
|
FINISHED |
| Object | HTTP Working Group |
E49793
|
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 Working Group | Statement: [RFC 2817, relatedWorkingGroup, HTTP Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP Working Group Context triple: [RFC 2817, relatedWorkingGroup, HTTP Working Group]
-
A.
HTTP Working Group
chosen
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
Web Hypertext Application Technology Working Group
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.
-
C.
TLS Working Group
The TLS Working Group is an IETF group responsible for developing and maintaining the Transport Layer Security (TLS) protocol and related technologies that secure communications over computer networks.
-
D.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
-
E.
OAuth Working Group
The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7d9c9c81909a0a0917deed0973 |
completed | April 2, 2026, 1:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26ac2f14081908deaf3945491af78 |
completed | April 5, 2026, 1:59 p.m. |
Created at: March 30, 2026, 8:53 p.m.