Triple
T2890089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schuylkill Action Network |
E63797
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional collaborative 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: regional collaborative network Context triple: [Schuylkill Action Network, instanceOf, regional collaborative network]
-
A.
regional chapter network
A regional chapter network is a coordinated system of local chapters within a defined geographic area that collaborate under a shared mission, governance structure, and resource framework to advance common goals.
-
B.
inter-district collaborative
An inter-district collaborative is a structured partnership among multiple school districts that share resources, expertise, and decision-making to improve educational services and outcomes across their combined communities.
-
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.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
E.
regional center
A regional center is an organization or facility that provides specialized services, coordination, and support to a defined geographic area, often acting as a hub for resources, administration, or expertise.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:07 p.m.