Triple
T28617989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast IDentity Online 2 |
E724314
|
entity |
| Predicate | supportsAuthenticatorType |
P40818
|
FINISHED |
| Object | hardware security keys |
—
|
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: hardware security keys | Statement: [Fast IDentity Online 2, supportsAuthenticatorType, hardware security keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAuthenticatorType Context triple: [Fast IDentity Online 2, supportsAuthenticatorType, hardware security keys]
-
A.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
-
B.
supportsSignInMethod
chosen
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
E.
supportsPermissionType
Indicates that one entity is capable of handling, allowing, or being configured with a specified type of permission.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a017a360f088190acd5933aa353e763 |
completed | May 11, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_6a0179d3f78c8190b1d2e8829619fa54 |
completed | May 11, 2026, 6:40 a.m. |
Created at: April 28, 2026, 4:32 a.m.