Triple

T9838270
Position Surface form Disambiguated ID Type / Status
Subject Baidu E239156 entity
Predicate hasProduct P3585 FINISHED
Object Baidu Search E239156 NE 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: Baidu Search | Statement: [Baidu, hasProduct, Baidu Search]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baidu Search
Context triple: [Baidu, hasProduct, Baidu Search]
  • A. Baidu chosen
    Baidu is a leading Chinese technology company best known for its dominant search engine and extensive work in artificial intelligence.
  • B. Yandex Search
    Yandex Search is a Russian-developed web search engine that powers Yandex’s ecosystem of online services and tools.
  • C. Google Search
    Google Search is a widely used web search engine developed by Google that allows users to find information, websites, images, and other content across the internet.
  • D. Bing
    Bing is Microsoft's web search engine that provides internet search, image, video, and mapping services.
  • E. Qwant
    Qwant is a French privacy-focused search engine that emphasizes user anonymity and does not track or profile its users.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84e314108190978324a4bdb959f8 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb34921b881909836ba0f5b42a27b completed April 2, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5d145ac8190ad10a4328216ef54 completed April 5, 2026, 3:24 a.m.
Created at: March 30, 2026, 8:33 p.m.