Triple
T7934164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft APIs |
E184248
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | Bing Search APIs |
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 Search APIs | Statement: [Microsoft APIs, includes, Bing Search APIs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bing Search APIs Context triple: [Microsoft APIs, includes, Bing Search APIs]
-
A.
Google Search
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.
Bing
chosen
Bing is Microsoft's web search engine that provides internet search, image, video, and mapping services.
-
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.
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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c0791e48190af18299c22f6a804 |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:08 p.m.