Triple
T26387122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guns Up hand sign |
E663310
|
entity |
| Predicate | gestureShape |
P78724
|
FINISHED |
| Object | extended index finger and thumb |
—
|
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: extended index finger and thumb | Statement: [Guns Up hand sign, gestureShape, extended index finger and thumb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gestureShape Context triple: [Guns Up hand sign, gestureShape, extended index finger and thumb]
-
A.
gestureForm
chosen
Indicates the specific physical configuration or movement pattern that characterizes a particular gesture within an interaction.
-
B.
gesture
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
C.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
D.
handMeaning
Indicates that one entity uses or positions its hand in a particular way to convey a specific meaning, message, or communicative intent toward another entity.
-
E.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bc2b288190ae10e6c27e5df786 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:23 p.m.