Triple
T14440816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache Lucene |
E358078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information retrieval library |
C34760
|
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: information retrieval library Context triple: [Apache Lucene, instanceOf, information retrieval library]
-
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.
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.
-
C.
online library catalog
An online library catalog is a digital system that allows users to search, browse, and access information about a library’s collection of books, media, and other resources via the internet.
-
D.
bibliographic service suite
A bibliographic service suite is an integrated set of tools and services that support the creation, management, discovery, and sharing of bibliographic records and related metadata across information systems.
-
E.
library and information service
A library and information service is an organized system that collects, manages, and provides access to information resources and related assistance to meet the informational, educational, and recreational needs of its users.
- F. None of above. chosen
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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:18 a.m.