Triple

T14371621
Position Surface form Disambiguated ID Type / Status
Subject Google Shopping E356369 entity
Predicate supportsUserAction P66543 FINISHED
Object click-through to merchant website 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: click-through to merchant website | Statement: [Google Shopping, supportsUserAction, click-through to merchant website]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsUserAction
Context triple: [Google Shopping, supportsUserAction, click-through to merchant website]
  • A. supportsUserInteraction chosen
    Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
  • B. supportsActionSpace
    Indicates that one entity is capable of enabling, handling, or being compatible with a specified action space for operations or behaviors.
  • C. supportedAct
    Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
  • D. supportsUse
    Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
  • E. supportsUserType
    Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
  • 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_69d8279163a081908aec45c0e3f1e02f completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8fb2082c8190b42cc5f2bab4f574 completed April 14, 2026, 7:04 p.m.
PD Predicate disambiguation batch_69de2a9cb3e081909f6b33fdd939bb9e completed April 14, 2026, 11:53 a.m.
Created at: April 10, 2026, 1:15 a.m.