Triple
T30879986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force Touch trackpad |
E786582
|
entity |
| Predicate | clickMechanism |
P24466
|
FINISHED |
| Object | haptic simulation |
—
|
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: haptic simulation | Statement: [Force Touch trackpad, clickMechanism, haptic simulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clickMechanism Context triple: [Force Touch trackpad, clickMechanism, haptic simulation]
-
A.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
B.
clickType
chosen
Indicates the specific kind or category of click interaction that occurred between a user and an interface element.
-
C.
launchMechanism
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
-
D.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
E.
focusMechanism
Indicates the method or process by which attention or emphasis is directed toward a particular entity or aspect within a context.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d99c0c81909eb316731f7d2feb |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.