Triple
T35297135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lam vong |
E1019402
|
entity |
| Predicate | handGestureType |
P16866
|
FINISHED |
| Object | soft curved hand gestures |
—
|
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: soft curved hand gestures | Statement: [lam vong, handGestureType, soft curved hand gestures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handGestureType Context triple: [lam vong, handGestureType, soft curved hand gestures]
-
A.
usesHandGestures
Indicates that an entity communicates or expresses itself by making deliberate movements or signals with its hands.
-
B.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
C.
gesture
chosen
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
D.
handPosition
Indicates the spatial location or orientation of a hand relative to a reference point or object.
-
E.
handConnection
Indicates a physical or functional linkage between hands, such as contact, holding, or coordinated interaction between them.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7901dce2c8190869190a338ec336c |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.