Triple

T4277397
Position Surface form Disambiguated ID Type / Status
Subject TPU E97074 entity
Predicate usedByService P1294 FINISHED
Object Google Search E72248 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: Google Search | Statement: [TPU, usedByService, Google Search]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Google Search
Context triple: [TPU, usedByService, Google Search]
  • A. Google Search chosen
    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.
  • B. Internet search
    Internet search is the process of using specialized software and algorithms to locate relevant information across the World Wide Web based on user queries.
  • C. Qwant
    Qwant is a French privacy-focused search engine that emphasizes user anonymity and does not track or profile its users.
  • D. 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.
  • E. Yandex Search
    Yandex Search is a Russian-developed web search engine that powers Yandex’s ecosystem of online services and tools.
  • 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_69b34544be3c819084d1ab82d29f90c5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3501ef1388190b0c968b069014a59 completed March 12, 2026, 11:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5b7b3b52c8190ae7c05448faf5558 completed March 14, 2026, 7:32 p.m.
Created at: March 12, 2026, 11:07 p.m.