Triple
T8288858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIDO2 |
E193845
|
entity |
| Predicate | standardizedBy |
P1371
|
FINISHED |
| Object | FIDO Alliance |
E724312
|
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: FIDO Alliance | Statement: [FIDO2, standardizedBy, FIDO Alliance]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FIDO Alliance Context triple: [FIDO2, standardizedBy, FIDO Alliance]
-
A.
FIDO Alliance
chosen
FIDO Alliance is an industry consortium that develops open, passwordless authentication standards to enhance online security and interoperability across devices and services.
-
B.
GlobalPlatform
GlobalPlatform is an international standards organization that defines specifications for secure chip technology and trusted digital services, including smart cards and secure elements.
-
C.
FIDO U2F
FIDO U2F is an open authentication standard that enables strong, phishing-resistant two-factor authentication using dedicated hardware security keys.
-
D.
FIDO2
FIDO2 is an open authentication standard that enables secure, passwordless logins using public-key cryptography across web and native applications.
-
E.
Gemalto
Gemalto is a digital security company known for providing smart cards, SIM cards, and secure software solutions for telecommunications, banking, and government identification.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c98e15c8190ac2a0b2a5ff834c9 |
completed | March 31, 2026, 7:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd952399dc8190914951d4e9e36c38 |
completed | April 1, 2026, 9:58 p.m. |
Created at: March 30, 2026, 5:52 p.m.