Triple
T8420498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas A&M School of Nursing |
E198836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Texas A&M University component |
C2719
|
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: Texas A&M University component Context triple: [Texas A&M School of Nursing, instanceOf, Texas A&M University component]
-
A.
Texas A&M University unit
chosen
A Texas A&M University unit is an organizational entity within the university—such as a college, department, division, or administrative office—responsible for specific academic, research, service, or operational functions.
-
B.
Texas A&M University alumnus
A Texas A&M University alumnus is an individual who has graduated from Texas A&M University, embodying its traditions, values, and educational legacy.
-
C.
Texas A&M University tradition
A Texas A&M University tradition is a long-standing, community-embraced practice or ritual that reflects and reinforces the university’s core values, history, and shared Aggie identity.
-
D.
Texas Tech University sports program
The Texas Tech University sports program encompasses a wide range of intercollegiate athletic teams, primarily known as the Red Raiders and Lady Raiders, competing at the NCAA Division I level and fostering school spirit, student-athlete development, and community engagement.
-
E.
Purdue University college
A Purdue University college is an academic division within Purdue University that organizes related departments and programs to provide specialized education, research, and outreach in a particular field of study.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:06 p.m.