Triple
T28977446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agriculture and Natural Resources Extension |
E734451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university extension program |
C7205
|
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 extension program Context triple: [Agriculture and Natural Resources Extension, instanceOf, university extension program]
-
A.
university extension service
chosen
A university extension service is an outreach arm of a university that delivers research-based education, resources, and support to communities, industries, and individuals beyond the campus.
-
B.
university farm
A university farm is an educational and research-focused agricultural facility operated by a university, where students and faculty engage in hands-on learning, experimentation, and demonstration of farming practices and technologies.
-
C.
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.
-
D.
university-affiliated program
A university-affiliated program is an organized set of activities, services, or studies that is formally connected to and overseen by a university, often leveraging its resources, faculty, and academic standards.
-
E.
university system
A university system is an integrated organizational framework that manages academic programs, students, faculty, resources, and administrative processes across one or more higher education institutions.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 9:09 a.m.