Triple
T6181049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldcoin |
E137941
|
entity |
| Predicate | claimsProperty |
P16616
|
FINISHED |
| Object | one person one proof design |
—
|
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: one person one proof design | Statement: [Worldcoin, claimsProperty, one person one proof design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsProperty Context triple: [Worldcoin, claimsProperty, one person one proof design]
-
A.
claimMethod
Indicates the method or procedure by which a claim is made, submitted, or executed.
-
B.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
C.
attributeClaim
chosen
Indicates that one entity asserts or specifies a particular attribute or property about another entity.
-
D.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
E.
claimNameGiven
Indicates that a specific name has been asserted or recorded as being given to an entity.
- 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.