Triple
T14718729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergey Brin |
E345751
|
entity |
| Predicate | notableWork |
P4
|
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: [Sergey Brin, notableWork, Google Search]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Google Search Context triple: [Sergey Brin, notableWork, 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.
OpenSearch
OpenSearch is an open-source, community-driven search and analytics engine and suite derived from Elasticsearch, used for full-text search, log analytics, and observability at scale.
-
C.
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.
-
D.
Qwant
Qwant is a French privacy-focused search engine that emphasizes user anonymity and does not track or profile its users.
-
E.
Microsoft Search API
Microsoft Search API is a developer interface that enables unified, intelligent search experiences across Microsoft 365 data and services.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98823408190b4b58a4c4a3fa3a3 |
completed | April 14, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0ce17f688190a86979cca8b88494 |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:29 a.m.