Triple

T9670579
Position Surface form Disambiguated ID Type / Status
Subject Head Crusher E234014 entity
Predicate usesGesture P16866 FINISHED
Object pinching fingers together while aligning them with a distant person’s head 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: pinching fingers together while aligning them with a distant person’s head | Statement: [Head Crusher, usesGesture, pinching fingers together while aligning them with a distant person’s head]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesGesture
Context triple: [Head Crusher, usesGesture, pinching fingers together while aligning them with a distant person’s head]
  • A. openingGesture
    Indicates an initial movement or action that begins or invites the start of an interaction, event, or sequence.
  • B. signatureGesture
    Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
  • C. hasTouchControls
    Indicates that an entity supports or is operated through touch-based input controls.
  • D. usesMovement
    Indicates that an entity performs or involves some form of movement as part of its action or behavior.
  • E. gesture chosen
    Indicates that an entity uses a bodily movement or sign to communicate or express something to another 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c3ec17081908c2da74a1d1f49da completed April 1, 2026, 10:29 p.m.
PD Predicate disambiguation batch_69ccd5b3239c8190b3ae3b9bd121e4bd completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:15 p.m.