Triple
T21191022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IGMP |
E522210
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | RFC 2236 |
—
|
NE NERFINISHED |
How this triple was built (3 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 2236 | Statement: [IGMP, definedIn, RFC 2236]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2236 Context triple: [IGMP, definedIn, RFC 2236]
-
A.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
B.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
C.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
D.
RFC 2203
RFC 2203 is an Internet standard that specifies the RPCSEC_GSS security protocol extension for providing authentication, integrity, and confidentiality in Remote Procedure Call (RPC) systems using GSS-API.
-
E.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2236 Target entity description: RFC 2236 is the Internet Engineering Task Force (IETF) specification that defines version 2 of the Internet Group Management Protocol (IGMPv2) used for managing IPv4 multicast group memberships.
-
A.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
B.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
C.
RFC 2026
RFC 2026 is an Internet Engineering Task Force (IETF) document that defines the standardization process and procedures for developing and approving Internet Standards.
-
D.
RFC 2203
RFC 2203 is an Internet standard that specifies the RPCSEC_GSS security protocol extension for providing authentication, integrity, and confidentiality in Remote Procedure Call (RPC) systems using GSS-API.
-
E.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
- F. None of above. chosen
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.