Triple
T17410253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saybrook Strip at The Game |
E423336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yale student tradition |
C2293
|
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: Yale student tradition Context triple: [Saybrook Strip at The Game, instanceOf, Yale student tradition]
-
A.
Yale University program
A Yale University program is an organized course of study or initiative offered by Yale that combines specific academic, professional, or extracurricular objectives, curricula, and resources under the university’s governance.
-
B.
Rutgers University tradition
A Rutgers University tradition is a recurring, community-valued practice or ritual—often tied to campus history, events, or symbols—that fosters shared identity and continuity among Rutgers students, alumni, and affiliates.
-
C.
university tradition
chosen
A university tradition is a recurring, institution-specific practice or ritual that embodies the shared history, values, and identity of a university community.
-
D.
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.
-
E.
Dartmouth College program
A Dartmouth College program is an organized set of academic or co-curricular offerings, activities, and resources designed by Dartmouth to provide structured learning, development, or engagement opportunities for its students or participants.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:46 a.m.