Triple
T34950063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C. E. "Red" Reed |
E1007966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Texas A&M University figure |
C7713
|
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 figure Context triple: [C. E. "Red" Reed, instanceOf, Texas A&M University figure]
-
A.
Texas A&M University unit
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
chosen
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.
member of the Texas A&M University System
A member of the Texas A&M University System is an institution or agency that operates under the governance of the System’s Board of Regents, sharing its mission, resources, and administrative oversight while maintaining its own specific academic or service focus.
-
E.
Texas Tech University organization
Texas Tech University organization represents any officially recognized group, department, or entity that operates within or is formally affiliated with Texas Tech University to support its academic, administrative, research, or student-life missions.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.