Triple
T21190992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPng Working Group |
E522209
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | RFC 1883 |
—
|
NE NERFINISHED |
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 1883 | Statement: [IPng Working Group, notableWork, RFC 1883]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1883 Context triple: [IPng Working Group, notableWork, RFC 1883]
-
A.
RFC 1883
chosen
RFC 1883 is the original Internet standard that defined the IPv6 protocol header format and core mechanisms before being superseded by RFC 2460.
-
B.
RFC 1889
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
-
C.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
D.
RFC 1831
RFC 1831 is the Internet standard that defines the core protocol specification for ONC (Open Network Computing) Remote Procedure Call.
-
E.
RFC 2813
RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.