Triple
T19586797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwarden |
E490125
|
entity |
| Predicate | supports2FA |
P40818
|
FINISHED |
| Object | FIDO2 security keys |
—
|
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: FIDO2 security keys | Statement: [Bitwarden, supports2FA, FIDO2 security keys]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FIDO2 security keys Context triple: [Bitwarden, supports2FA, FIDO2 security keys]
-
A.
FIDO2
chosen
FIDO2 is an open authentication standard that enables secure, passwordless logins using public-key cryptography across web and native applications.
-
B.
FIDO U2F
FIDO U2F is an open authentication standard that enables strong, phishing-resistant two-factor authentication using dedicated hardware security keys.
-
C.
FIDO UAF
FIDO UAF (Universal Authentication Framework) is a passwordless authentication standard developed by the FIDO Alliance that enables secure, biometric-based login using public-key cryptography.
-
D.
FIDO
FIDO is a NASA Mission Control flight dynamics officer responsible for tracking spacecraft trajectories and planning orbital maneuvers during missions.
-
E.
YubiKey
YubiKey is a hardware security key used for strong two-factor and passwordless authentication across various online services and devices.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640523d10819091320a61456f6437 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.