Triple
T596600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Racing Team |
E17397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university research team |
C4221
|
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: university research team Context triple: [Stanford Racing Team, instanceOf, university research team]
-
A.
research university
A research university is a higher education institution that prioritizes the creation of new knowledge through extensive research activities while offering a broad range of undergraduate and graduate academic programs.
-
B.
university research program
A university research program is an organized, often interdisciplinary initiative within a higher education institution that supports systematic investigation, innovation, and scholarly inquiry in specific fields or themes.
-
C.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
D.
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.
-
E.
research organization
A research organization is an institution that systematically investigates specific questions or problems to generate new knowledge, technologies, or insights, often within scientific, academic, or applied domains.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:33 p.m.