Triple
T20978171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile IPv6 |
E516680
|
entity |
| Predicate | updatesByRFC |
P132457
|
FINISHED |
| Object | RFC 6275 |
—
|
NE NERFINISHED |
How this triple was built (4 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 6275 | Statement: [Mobile IPv6, updatesByRFC, RFC 6275]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6275 Context triple: [Mobile IPv6, updatesByRFC, RFC 6275]
-
A.
RFC 7525
RFC 7525 is an IETF Best Current Practice document that provides recommendations for securely configuring Transport Layer Security (TLS) and Datagram TLS (DTLS) for Internet protocols.
-
B.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
C.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
D.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
E.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
- 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 6275 Target entity description: RFC 6275 is the IETF standard that specifies the core protocol for Mobile IPv6, enabling IP mobility support for IPv6 nodes across different networks.
-
A.
RFC 7525
RFC 7525 is an IETF Best Current Practice document that provides recommendations for securely configuring Transport Layer Security (TLS) and Datagram TLS (DTLS) for Internet protocols.
-
B.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
C.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
D.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
E.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesByRFC Context triple: [Mobile IPv6, updatesByRFC, RFC 6275]
-
A.
updatesFrom
chosen
Indicates that one entity is revised, modified, or brought to a newer state based on information, changes, or content originating from another entity.
-
B.
updatesType
Indicates that one entity modifies, revises, or replaces the type or classification of another entity.
-
C.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
D.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
E.
updateFor
Indicates that one entity is modified or refreshed in response to changes or conditions associated with another entity.
- F. None of above.
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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba65b0881908bc00981053edb68 |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:47 p.m.