Triple
T14395893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4791 |
E356946
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | RFC 4918 |
E699617
|
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: RFC 4918 | Statement: [RFC 4791, relatedStandard, RFC 4918]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4918 Context triple: [RFC 4791, relatedStandard, RFC 4918]
-
A.
RFC 4918
chosen
RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
-
B.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
C.
RFC 2518
RFC 2518 is the original IETF specification that defined the Web Distributed Authoring and Versioning (WebDAV) protocol for collaborative web content authoring and file management over HTTP.
-
D.
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.
-
E.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90826f908190b3969af9b7cf922f |
completed | April 14, 2026, 7:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd551cbdb08190a9ea53e607f2555b |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 1:17 a.m.