Triple
T7296553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet search |
E164535
|
entity |
| Predicate | commonProviders |
P17473
|
FINISHED |
| Object | Baidu |
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 | Statement: [Internet search, commonProviders, Baidu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baidu Context triple: [Internet search, commonProviders, Baidu]
-
A.
Baidu
chosen
Baidu is a leading Chinese technology company best known for its dominant search engine and extensive work in artificial intelligence.
-
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.
Yandex
Yandex is a major Russian multinational technology company best known for its internet search engine and wide range of online services.
-
D.
Google
Google is a multinational technology company best known for its search engine and wide range of internet-related products and services, including Android, YouTube, and cloud computing.
-
E.
Bing
Bing is Microsoft's web search engine that provides internet search, image, video, and mapping 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6f041f4a88190b85cff1ee5f9a6d0 |
completed | March 27, 2026, 9:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e547c7b88190b792495efb3a215c |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3 p.m.