Triple
T611231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Physical Review Journals Archive |
E12103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | physics literature database |
C1031
|
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: physics literature database Context triple: [Physical Review Journals Archive, instanceOf, physics literature database]
-
A.
bibliographic database
chosen
A bibliographic database is a structured collection of references to published literature, such as books, articles, and reports, organized to support efficient search, retrieval, and management of bibliographic information.
-
B.
research library
A research library is a specialized institution that collects, organizes, preserves, and provides access to scholarly resources and reference services to support advanced study and original research.
-
C.
body of scientific work
A body of scientific work is the organized collection of research outputs, including studies, experiments, analyses, and publications, that collectively advance understanding within a particular scientific domain or across multiple related fields.
-
D.
unit of the American Physical Society
A unit of the American Physical Society is a subdivision of the organization, such as a division, topical group, forum, or section, that focuses on a specific area of physics or professional interest to support research, communication, and community-building among its members.
-
E.
publication
A publication is a finalized work of content (such as an article, book, or report) that has been formally released and made accessible to an audience through a chosen medium.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:35 p.m.