Triple
T6181053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldcoin |
E137941
|
entity |
| Predicate | regulatorAction |
P69525
|
FINISHED |
| Object | suspended in Kenya |
—
|
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: suspended in Kenya | Statement: [Worldcoin, regulatorAction, suspended in Kenya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatorAction Context triple: [Worldcoin, regulatorAction, suspended in Kenya]
-
A.
regulatorRole
Indicates that one entity serves in an official capacity to oversee, control, or enforce rules and standards governing another entity or activity.
-
B.
regulatorEstablished
Indicates that an entity has formally created, instituted, or set up a regulatory body or authority.
-
C.
regulateBy
Indicates that one entity exercises control, guidance, or governance over another entity’s behavior, operation, or state through rules, mechanisms, or constraints.
-
D.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
-
E.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.