Triple

T3426963
Position Surface form Disambiguated ID Type / Status
Subject Google Search E72248 entity
Predicate competesWith P1375 FINISHED
Object Bing E56719 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: Bing | Statement: [Google Search, competesWith, Bing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bing
Context triple: [Google Search, competesWith, Bing]
  • A. Bing chosen
    Bing is Microsoft's web search engine that provides internet search, image, video, and mapping services.
  • B. Goole
    Goole is an inland port town in the East Riding of Yorkshire, England, known for its significant docks and role in regional maritime trade.
  • C. DuckDuckGo
    DuckDuckGo is a privacy-focused internet search engine that emphasizes not tracking users or personalizing search results based on their data.
  • D. Cốc Cốc
    Cốc Cốc is a Vietnamese web browser and search engine tailored to local users, offering features like improved downloading, integrated ad-blocking, and support for Vietnamese language and services.
  • E. Baidu
    Baidu is a leading Chinese technology company best known for its dominant search engine and extensive work in artificial intelligence.
  • 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_69ad85ae14308190bcbc25cfa0246c0b completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb982792c8190b1163eee4252210f completed March 8, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69b35478448481908e1c0f717d99f992 completed March 13, 2026, 12:04 a.m.
Created at: March 8, 2026, 3:15 p.m.