Triple
T7689739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V for Victory sign |
E174213
|
entity |
| Predicate | gestureForm |
P78724
|
FINISHED |
| Object | one-handed gesture |
—
|
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: one-handed gesture | Statement: [V for Victory sign, gestureForm, one-handed gesture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gestureForm Context triple: [V for Victory sign, gestureForm, one-handed gesture]
-
A.
gesture
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
B.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
C.
recognizedSignLanguage
Indicates that one entity has correctly identified or understood a sign language used or produced by another 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.
governingForm
Indicates that one entity specifies or embodies the authoritative rules, structure, or format that control or regulate another entity.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c706d0c1708190a3e74523997814b8 |
completed | March 27, 2026, 10:38 p.m. |
Created at: March 27, 2026, 4:02 p.m.