Triple

T29792899
Position Surface form Disambiguated ID Type / Status
Subject Popular Demand E756458 entity
Predicate hasCustomerReception P66549 FINISHED
Object strong customer appeal 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: strong customer appeal | Statement: [Popular Demand, hasCustomerReception, strong customer appeal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCustomerReception
Context triple: [Popular Demand, hasCustomerReception, strong customer appeal]
  • A. hasReception
    Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
  • B. hasOnlineReception
    Indicates that an entity provides or supports a reception, front-desk, or greeting function through online or digital channels rather than solely in person.
  • C. hasCustomerServices
    Indicates that an entity provides or is associated with one or more customer service functions or offerings.
  • D. hasCustomers
    Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
  • E. hasReviewReception chosen
    Indicates that an entity has received a critical or evaluative review describing how it was received or perceived.
  • 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_69f22454583081908927516cb9938d1d completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fcd867f36081908c88c55a6a1404c1 completed May 7, 2026, 6:22 p.m.
PD Predicate disambiguation batch_69fcd1f47b188190b4cf4b4c748d9d03 completed May 7, 2026, 5:55 p.m.
Created at: April 29, 2026, 5:13 p.m.