Triple
T15217935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST Special Database 1 |
E363687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NIST special database |
C9832
|
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: NIST special database Context triple: [NIST Special Database 1, instanceOf, NIST special database]
-
A.
NIST Special Publication series
The NIST Special Publication series is a collection of authoritative technical reports and guidelines issued by the National Institute of Standards and Technology covering standards, best practices, and research across diverse scientific and technological domains.
-
B.
bibliometric database
A bibliometric database is a structured collection of publication and citation data used to analyze research output, impact, and scholarly networks.
-
C.
bibliographic database
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.
-
D.
federal government database
A federal government database is a centralized, secure digital repository used by national government agencies to store, manage, and retrieve official records, data, and information for administrative, regulatory, and public service purposes.
-
E.
federal government database
chosen
A federal government database is a centralized, electronically managed collection of structured data maintained by national government agencies to store, process, and retrieve information for administrative, regulatory, and public service purposes.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:11 a.m.