Triple
T29030423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Launchpad |
E737711
|
entity |
| Predicate | gestureDefault |
P78724
|
FINISHED |
| Object | pinch with thumb and three fingers on trackpad |
—
|
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: pinch with thumb and three fingers on trackpad | Statement: [Launchpad, gestureDefault, pinch with thumb and three fingers on trackpad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gestureDefault Context triple: [Launchpad, gestureDefault, pinch with thumb and three fingers on trackpad]
-
A.
gesture
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
B.
gestureForm
chosen
Indicates the specific physical configuration or movement pattern that characterizes a particular gesture within an interaction.
-
C.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
D.
openingGesture
Indicates an initial movement or action that begins or invites the start of an interaction, event, or sequence.
-
E.
usesHandGestures
Indicates that an entity communicates or expresses itself by making deliberate movements or signals with its hands.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603953f88190a8805a698456ab58 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:55 a.m.