Triple
T19586796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwarden |
E490125
|
entity |
| Predicate | supports2FA |
P40818
|
FINISHED |
| Object | authenticator apps |
—
|
LITERAL 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: authenticator apps | Statement: [Bitwarden, supports2FA, authenticator apps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports2FA Context triple: [Bitwarden, supports2FA, authenticator apps]
-
A.
secondFactor
Indicates that one entity serves as the second factor or component in a multiplicative or combinational relationship with another entity.
-
B.
supports2G
Indicates that one entity provides compatibility with or operational backing for 2G (second-generation) mobile network technology for another entity.
-
C.
supportsSignInMethod
chosen
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
D.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
-
E.
supportsLockoutType
Indicates that one entity is compatible with or able to operate using a specified lockout type.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640523d10819091320a61456f6437 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.