Triple
T24849053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HST |
E621834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative program |
C12274
|
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: collaborative program Context triple: [HST, instanceOf, collaborative program]
-
A.
collaborative project
chosen
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
B.
interdisciplinary program
An interdisciplinary program is an academic course of study that integrates methods, perspectives, and content from multiple disciplines to address complex questions or problems that cannot be fully understood through a single field alone.
-
C.
library cooperative program
A library cooperative program is a collaborative arrangement among multiple libraries to share resources, services, and expertise in order to expand access and reduce costs for their communities.
-
D.
community-based program
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
E.
fellowship program
A fellowship program is a structured, time-bound opportunity that provides individuals with financial support, mentorship, and professional development to advance their skills, research, or leadership in a specific field.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:20 a.m.