Triple
T20978260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proxy Mobile IPv6 |
E516681
|
entity |
| Predicate | hasExtension |
P455
|
FINISHED |
| Object | RFC 5844 |
—
|
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 5844 | Statement: [Proxy Mobile IPv6, hasExtension, RFC 5844]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5844 Context triple: [Proxy Mobile IPv6, hasExtension, RFC 5844]
-
A.
RFC 5044
RFC 5044 is an IETF standard that defines the protocol architecture and mechanisms for iWARP, enabling RDMA operations over TCP/IP networks.
-
B.
RFC 4844
RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
-
C.
RFC 5894
RFC 5894 is an Internet Engineering Task Force (IETF) document that provides the design rationale and background for the updated Internationalized Domain Names in Applications (IDNA2008) standard.
-
D.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
E.
RFC 7344
RFC 7344 is an Internet Engineering Task Force (IETF) standard that specifies automated mechanisms for maintaining DNSSEC delegation trust using CDS and related records.
- 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 5844 Target entity description: RFC 5844 is an IETF specification that defines how Proxy Mobile IPv6 can be used to provide network-based mobility management for IPv4 traffic and dual-stack hosts.
-
A.
RFC 5044
RFC 5044 is an IETF standard that defines the protocol architecture and mechanisms for iWARP, enabling RDMA operations over TCP/IP networks.
-
B.
RFC 4844
RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
-
C.
RFC 5894
RFC 5894 is an Internet Engineering Task Force (IETF) document that provides the design rationale and background for the updated Internationalized Domain Names in Applications (IDNA2008) standard.
-
D.
RFC 3584
RFC 3584 is an IETF standard that specifies coexistence and transition mechanisms between SNMPv1, SNMPv2c, and SNMPv3, including definitions such as the SNMP-COMMUNITY-MIB.
-
E.
RFC 7344
RFC 7344 is an Internet Engineering Task Force (IETF) standard that specifies automated mechanisms for maintaining DNSSEC delegation trust using CDS and related records.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba65b0881908bc00981053edb68 |
completed | April 21, 2026, 4:23 a.m. |
Created at: April 16, 2026, 1:47 p.m.