Triple
T23046243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World ID |
E573884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital identity protocol |
C994
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: digital identity protocol Context triple: [World ID, instanceOf, digital identity protocol]
-
A.
digital certificate
A digital certificate is an electronic credential issued by a trusted authority that binds a public key to an entity’s identity, enabling secure and authenticated communication over networks.
-
B.
identity document technology
Identity document technology encompasses the systems, materials, and processes used to create, secure, verify, and manage official credentials that authenticate an individual’s identity.
-
C.
identity verification platform
An identity verification platform is a system that securely validates and authenticates individuals’ identities using documents, biometrics, and data checks to prevent fraud and ensure trust in digital interactions.
-
D.
cryptographic protocol
chosen
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
-
E.
token identity theory
Token identity theory is the view in philosophy of mind that each particular mental event is identical to some particular physical event in the brain, even though there need not be a one-to-one identity between types of mental states and types of physical states.
- F. None of above.
Provenance (1 batch)
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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:54 p.m.