Triple
T33801309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard affiliates |
E866226
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university community subgroup |
C2585
|
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: university community subgroup Context triple: [Harvard affiliates, instanceOf, university community subgroup]
-
A.
university campus group
A university campus group is an organized collection of students, faculty, or staff who share common interests, goals, or activities and operate within a university setting to foster community, learning, and engagement.
-
B.
subcommunity
chosen
A subcommunity is a smaller, more specialized group of individuals within a larger community who share specific interests, characteristics, or goals that distinguish them from the broader whole.
-
C.
university mission group
A university mission group is a dedicated organization within a university that plans, coordinates, and supports mission-oriented activities, such as community service, outreach, and faith-based or social impact initiatives, for students and staff.
-
D.
undergraduate student organization
An undergraduate student organization is a formally recognized group of college students who collaborate around shared interests, goals, or identities to provide activities, support, and community within the university.
-
E.
intellectual community
An intellectual community is a group of individuals who share, develop, and critically engage with ideas, knowledge, and inquiry around common interests or disciplines.
- 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_69f3499057fc81909d862b1309a3bd71 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.