Triple

T33105213
Position Surface form Disambiguated ID Type / Status
Subject Shinsuke Nakamura E847169 entity
Predicate usesEntranceGesture P139008 FINISHED
Object trademark body contortions and poses 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: trademark body contortions and poses | Statement: [Shinsuke Nakamura, usesEntranceGesture, trademark body contortions and poses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesEntranceGesture
Context triple: [Shinsuke Nakamura, usesEntranceGesture, trademark body contortions and poses]
  • A. hasAutomaticEntrance
    Indicates that an entity is equipped with an entrance that operates automatically (e.g., opens or closes without manual effort).
  • B. hasEntrance
    Indicates that one entity possesses or provides an entry point or access way to another entity or space.
  • C. hasEntranceOn
    Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
  • D. usesHandGestures chosen
    Indicates that an entity communicates or expresses itself by making deliberate movements or signals with its hands.
  • E. hasEntranceStyle
    Indicates the architectural or design style characterizing the entrance of an entity (such as a building or space).
  • 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_69f3495686508190b76bf20fa5e00bf7 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6db6af1d88190989810182354d60f completed May 3, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69f6d82d068c8190940a3200ed760e38 completed May 3, 2026, 5:07 a.m.
Created at: May 1, 2026, 1:26 a.m.