Triple
T26317859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WAIS |
E662021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | networked information retrieval system |
C36543
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: networked information retrieval system Context triple: [WAIS, instanceOf, networked information retrieval system]
-
A.
information retrieval protocol
An information retrieval protocol is a standardized set of rules and procedures that governs how queries are formulated, transmitted, processed, and responded to in order to locate and deliver relevant information from distributed systems or databases.
-
B.
information retrieval library
An information retrieval library is a software component that provides tools and algorithms for indexing, searching, and ranking documents or data to efficiently satisfy user queries.
-
C.
online public access system
chosen
An online public access system is a web-based interface that allows users to search, retrieve, and interact with information or resources from a publicly accessible database or catalog.
-
D.
network information service
A network information service is a system that centrally stores, manages, and distributes configuration and directory data (such as user accounts, hostnames, and services) across computers in a network.
-
E.
bibliographic database provider
A bibliographic database provider is an organization or service that collects, curates, indexes, and delivers structured metadata about publications and scholarly works for search, discovery, and analysis.
- F. None of above.
Provenance (1 batch)
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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:26 p.m.