Triple
T10329338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permissions API |
E242836
|
entity |
| Predicate | definesEventHandler |
P53490
|
FINISHED |
| Object | PermissionStatus.onchange |
—
|
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: PermissionStatus.onchange | Statement: [Permissions API, definesEventHandler, PermissionStatus.onchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEventHandler Context triple: [Permissions API, definesEventHandler, PermissionStatus.onchange]
-
A.
dealtWithEvent
Indicates that an entity has handled, responded to, or otherwise taken action to address a particular event.
-
B.
interpretsEvent
Indicates that an entity analyzes and assigns meaning or significance to an event.
-
C.
instrumentHandled
Indicates that an entity uses, operates, or physically manipulates an instrument or tool to perform an action or task.
-
D.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
E.
hasHandler
chosen
Indicates that one entity is responsible for managing, controlling, or processing another 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.