Triple
T5818157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Harvard Crimson |
E129037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Harvard University student organization |
C10645
|
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 University student organization Context triple: [The Harvard Crimson, instanceOf, Harvard University student organization]
-
A.
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.
-
B.
Harvard University affiliate
chosen
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.
-
C.
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.
-
D.
Stanford University organization
Stanford University organization: An entity within or formally affiliated with Stanford University that contributes to its educational, research, administrative, or community mission through structured activities, governance, or services.
-
E.
Harvard University alumnus
A Harvard University alumnus is an individual who has successfully completed a degree or formal program of study at Harvard University.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:53 p.m.