Triple
T31804809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron Crazies |
E811843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke University tradition |
C57513
|
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: Duke University tradition Context triple: [Cameron Crazies, instanceOf, Duke University tradition]
-
A.
Duke University tradition
chosen
A Duke University tradition is a recurring, community-valued practice or ritual—often tied to campus life, athletics, or institutional history—that fosters shared identity and continuity among Duke students, alumni, and affiliates.
-
B.
Duke University school
A Duke University school is an academic division within Duke University that offers specialized undergraduate, graduate, and professional programs, integrating teaching, research, and service in a particular field of study.
-
C.
Duke University campus
Duke University campus is a picturesque, Gothic-inspired academic environment in Durham, North Carolina, featuring iconic stone architecture, expansive wooded grounds, and state-of-the-art research and athletic facilities.
-
D.
Duke University facility
A Duke University facility is any physical location, building, or infrastructure owned, leased, or operated by Duke University that supports its academic, research, healthcare, residential, or administrative functions.
-
E.
Duke University song
A Duke University song is a musical composition officially or traditionally associated with Duke University, often performed at campus events to express school spirit, celebrate its history, and unify students, alumni, and supporters.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:42 p.m.