Triple

T17676718
Position Surface form Disambiguated ID Type / Status
Subject Google Stadia E440658 entity
Predicate accessMethod P5872 FINISHED
Object Google Chrome NE NERFINISHED

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 Chrome | Statement: [Google Stadia, accessMethod, Google Chrome]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Google Chrome
Context triple: [Google Stadia, accessMethod, Google Chrome]
  • A. Google Chrome chosen
    Google Chrome is a widely used cross-platform web browser developed by Google, known for its speed, simplicity, and integration with Google services.
  • B. Chrome
    Chrome is an unincorporated rural community located in Glenn County, California.
  • C. Yandex Browser
    Yandex Browser is a web browser developed by the Russian company Yandex that emphasizes speed, security, and integration with Yandex’s online services.
  • D. Chromium web browser
    Chromium web browser is an open-source, multi-platform web browser that serves as the foundation for Google Chrome and many other Chromium-based browsers.
  • E. 360 Secure Browser
    360 Secure Browser is a Chinese web browser developed by Qihoo 360, known for its built-in security features and dual-engine rendering support.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6d9ab88190ab0e25eac8b0101c completed April 19, 2026, 6 a.m.
Created at: April 10, 2026, 10:01 a.m.