Triple
T28596272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki site administrators |
E723778
|
entity |
| Predicate | hasPermissionTo |
P178972
|
FINISHED |
| Object | create and delete user groups |
—
|
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: create and delete user groups | Statement: [MediaWiki site administrators, hasPermissionTo, create and delete user groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPermissionTo Context triple: [MediaWiki site administrators, hasPermissionTo, create and delete user groups]
-
A.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
B.
isGrantedTo
chosen
Indicates that a right, permission, or privilege is formally given by one entity to another.
-
C.
hasPermit
Indicates that an entity possesses an official authorization or license granting it permission to perform a specific activity or hold a certain status.
-
D.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
E.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 4:21 a.m.