Triple
T503559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Engineering at Texas A&M University |
E10451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | college within a university |
C2977
|
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: college within a university Context triple: [College of Engineering at Texas A&M University, instanceOf, college within a university]
-
A.
private university
A private university is a higher education institution that is independently funded and operated, primarily through tuition, donations, and endowments rather than direct government support.
-
B.
university
A university is an institution of higher education and research that grants academic degrees and fosters advanced learning across diverse fields of study.
-
C.
university collaboration
University collaboration is the structured partnership between universities and external entities (such as other academic institutions, industry, government, or communities) to jointly pursue research, education, innovation, and resource sharing.
-
D.
state university system
A state university system is a coordinated network of public higher education institutions within a state, governed by a central authority to manage funding, policy, and academic standards.
-
E.
university governing body
A university governing body is a formal group of appointed or elected individuals responsible for setting the institution’s strategic direction, overseeing its policies and finances, and ensuring accountability and compliance with legal and educational standards.
- F. None of above. chosen
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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.