Triple
T22059327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine library network |
E545109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | resource-sharing network |
C10807
|
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: resource-sharing network Context triple: [Maine library network, instanceOf, resource-sharing network]
-
A.
collaborative networks
Collaborative networks are interconnected groups of individuals or organizations that share resources, knowledge, and responsibilities to achieve common goals more effectively than they could independently.
-
B.
regional collaborative network
chosen
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
C.
research network
A research network is a structured system of interconnected researchers, institutions, and resources that collaboratively generate, share, and advance knowledge within and across disciplines.
-
D.
state-controlled network of organizations
A state-controlled network of organizations is a coordinated system of entities whose structures, activities, and decision-making are centrally directed or heavily influenced by government authorities to achieve political, economic, or social objectives.
-
E.
habitat network
A habitat network is an interconnected system of natural areas and corridors that facilitates the movement, survival, and genetic exchange of species across a landscape.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.