Triple
T6181048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldcoin |
E137941
|
entity |
| Predicate | verificationOutcome |
P42634
|
FINISHED |
| Object | unique World ID |
—
|
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: unique World ID | Statement: [Worldcoin, verificationOutcome, unique World ID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationOutcome Context triple: [Worldcoin, verificationOutcome, unique World ID]
-
A.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
B.
confirmationOutcome
chosen
Indicates the result or status produced when a prior action, request, or assertion is checked and confirmed.
-
C.
verificationSystem
Indicates that an entity functions as or is associated with a system responsible for checking, validating, or confirming the correctness or authenticity of something.
-
D.
confirmationMethod
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
E.
valuationStatus
Indicates the current state or condition of an entity’s assessed value within a valuation process (e.g., pending, active, finalized, or invalid).
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c060fdf7ac8190a0e887907ec9a922 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.