Triple
T17498889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon OpenSearch Service |
E426143
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | OpenSearch |
—
|
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: OpenSearch | Statement: [Amazon OpenSearch Service, supports, OpenSearch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenSearch Context triple: [Amazon OpenSearch Service, supports, OpenSearch]
-
A.
OpenSearch
chosen
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.
-
B.
Qwant
Qwant is a French privacy-focused search engine that emphasizes user anonymity and does not track or profile its users.
-
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.
Brave Search
Brave Search is a privacy-focused, independent search engine developed by Brave that emphasizes user anonymity and reduced tracking.
-
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 (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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4521028048190aa7c4023a72a12f4 |
completed | April 19, 2026, 3:54 a.m. |
Created at: April 10, 2026, 5:48 a.m.