Triple
T35783539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Law School Association |
E1034499
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Harvard Law School organization |
C62637
|
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: Harvard Law School organization Context triple: [Harvard Law School Association, instanceOf, Harvard Law School organization]
-
A.
Harvard Business School organization
A Harvard Business School organization is a structured group within the HBS community—such as a club, center, or initiative—formed to advance specific academic, professional, or social objectives aligned with the school’s mission.
-
B.
Yale University organization
A Yale University organization is a formally recognized group or entity within Yale that brings together students, faculty, staff, or alumni around shared academic, professional, cultural, social, or service-oriented interests and activities.
-
C.
Yale Law School center
A Yale Law School center is an institutional unit within Yale Law School dedicated to specialized legal research, education, and policy engagement in a particular field of law.
-
D.
Harvard University affiliate
A Harvard University affiliate is an individual or entity formally connected to Harvard through enrollment, employment, appointment, or recognized partnership, granting them certain institutional rights, privileges, or associations.
-
E.
Harvard University facility
A Harvard University facility is any physical building, space, or infrastructure owned, leased, or operated by Harvard that supports its academic, research, residential, administrative, or community functions.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.