Triple
T22489354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clipboard API |
E555972
|
entity |
| Predicate | permissionName |
P148410
|
FINISHED |
| Object | clipboard-read |
—
|
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: clipboard-read | Statement: [Clipboard API, permissionName, clipboard-read]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permissionName Context triple: [Clipboard API, permissionName, clipboard-read]
-
A.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
B.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
C.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
D.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
E.
authorizationCheck
Indicates that a verification is performed to determine whether an entity has the required permissions to perform a specific action or access a particular resource.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3f3b4c819092bfe6495c61db46 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.