Triple
T14586774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Park Service cultural resources information systems |
E342336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital information system |
C224
|
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: digital information system Context triple: [National Park Service cultural resources information systems, instanceOf, digital information system]
-
A.
information system
chosen
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
-
B.
digital information management framework
A digital information management framework is a structured set of principles, processes, and tools for systematically capturing, organizing, securing, accessing, and governing digital data and content across its lifecycle.
-
C.
digital repository
A digital repository is a managed, long-term storage system that collects, preserves, and provides organized access to digital content and associated metadata.
-
D.
digital platform
A digital platform is an online infrastructure that facilitates interactions, transactions, or value exchange between users, services, or systems through integrated digital tools and interfaces.
-
E.
information services provider
An information services provider is an entity that collects, processes, and delivers data, analysis, or knowledge-based content to users or organizations through various digital or physical channels.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:24 a.m.