Triple

T19225184
Position Surface form Disambiguated ID Type / Status
Subject Hook ’em Horns hand sign E480719 entity
Predicate visualSimilarity P94757 FINISHED
Object sign of the horns 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: sign of the horns gesture | Statement: [Hook ’em Horns hand sign, visualSimilarity, sign of the horns gesture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: visualSimilarity
Context triple: [Hook ’em Horns hand sign, visualSimilarity, sign of the horns gesture]
  • A. visualFeature
    Indicates a relationship where one entity possesses or exhibits a particular visual characteristic or attribute of another entity.
  • B. hasSimilarityTo chosen
    Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
  • C. lessSimilarTo
    Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
  • D. visualCompanion
    Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
  • E. namedForSimilarityTo
    Indicates that one entity is given its name because of a perceived resemblance or likeness 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_69d8e8ccb8f48190ad420098e74fb1db completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fa97287c8190b85184a512a9c960 completed April 20, 2026, 10:06 a.m.
PD Predicate disambiguation batch_69e4dcfae6f081909cc173cf71a5005c completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:24 p.m.