Triple
T12515497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4880 |
E299181
|
entity |
| Predicate | specifies |
P773
|
FINISHED |
| Object | OpenPGP packet types |
E35340
|
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: OpenPGP packet types | Statement: [RFC 4880, specifies, OpenPGP packet types]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenPGP packet types Context triple: [RFC 4880, specifies, OpenPGP packet types]
-
A.
Pgp
Pgp is a membrane transport protein that functions as an ATP-dependent efflux pump, playing a key role in multidrug resistance by exporting various drugs and xenobiotics out of cells.
-
B.
PGP
chosen
PGP (Pretty Good Privacy) is an encryption program that provides cryptographic privacy and authentication for data communication, most notably for securing emails and files.
-
C.
RFC 4880
RFC 4880 is the Internet Engineering Task Force (IETF) standard that defines the OpenPGP message format for encrypted and signed data.
-
D.
PKCS #7
PKCS #7 is a cryptographic standard that defines the syntax for digitally signing and encrypting data, forming the basis for formats like S/MIME and CMS (Cryptographic Message Syntax).
-
E.
PKCS #1
PKCS #1 is a cryptographic standard that defines the mathematical properties, formats, and padding schemes for implementing RSA encryption and digital signatures.
- 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_69f64bbd58b88190baeb99380babf64f |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.