Triple

T22375593
Position Surface form Disambiguated ID Type / Status
Subject Thunderbird project E553143 entity
Predicate supportsOpenStandards P1587 FINISHED
Object OpenPGP NE NERFINISHED

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 | Statement: [Thunderbird project, supportsOpenStandards, OpenPGP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OpenPGP
Context triple: [Thunderbird project, supportsOpenStandards, OpenPGP]
  • A. 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.
  • B. 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.
  • C. GNU Privacy Guard
    GNU Privacy Guard is a free, open-source implementation of the OpenPGP standard used for encrypting and signing data and communications.
  • D. GpgOL
    GpgOL is an email encryption and signing plugin for Microsoft Outlook that integrates GnuPG functionality into the mail client.
  • E. RFC 4880 chosen
    RFC 4880 is the Internet Engineering Task Force (IETF) standard that defines the OpenPGP message format for encrypted and signed data.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15807cb748190abd9adc08ca1ad4f completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:45 p.m.