Triple
T12515544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2440 |
E299182
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 4880 |
E299181
|
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 4880 | Statement: [RFC 2440, obsoletedBy, RFC 4880]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4880 Context triple: [RFC 2440, obsoletedBy, RFC 4880]
-
A.
RFC 4880
chosen
RFC 4880 is the Internet Engineering Task Force (IETF) standard that defines the OpenPGP message format for encrypted and signed data.
-
B.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
C.
RFC 8017
RFC 8017 is the Internet standard that specifies the RSA Cryptography Standard (PKCS #1), defining algorithms and formats for RSA encryption and digital signatures.
-
D.
PGP
PGP (Pretty Good Privacy) is an encryption program that provides cryptographic privacy and authentication for data communication, most notably for securing emails and files.
-
E.
RFC 7748
RFC 7748 is an IETF standard that specifies the elliptic curves Curve25519 and Curve448 for secure key exchange in modern cryptographic protocols.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9541f80148190976d1d912fe155d0 |
completed | April 10, 2026, 7:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65eac74608190a6f1941ed5a05212 |
completed | May 2, 2026, 8:29 p.m. |
Created at: April 8, 2026, 9:57 p.m.