Triple
T33435764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vibration API |
E856234
|
entity |
| Predicate | exampleCall |
P176618
|
FINISHED |
| Object | navigator.vibrate(200) |
—
|
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: navigator.vibrate(200) | Statement: [Vibration API, exampleCall, navigator.vibrate(200)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleCall Context triple: [Vibration API, exampleCall, navigator.vibrate(200)]
-
A.
initialCall
Indicates that an interaction represents the first or starting phone call or communication event between the involved entities.
-
B.
displayCall
Indicates that one entity presents or shows a call (such as a phone call or function call) to another entity or to a user interface.
-
C.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
D.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
E.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.