Triple
T4368902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas A&M AgriLife Extension Service |
E98845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cooperative extension service |
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: cooperative extension service Context triple: [Texas A&M AgriLife Extension Service, instanceOf, cooperative extension service]
-
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.
agricultural school
An agricultural school is an educational institution that provides specialized training and instruction in farming, agronomy, animal husbandry, and related agricultural sciences and technologies.
-
C.
school of natural resources
A school of natural resources is an academic unit within a college or university dedicated to studying, managing, and conserving natural ecosystems and resources through interdisciplinary education and research.
-
D.
department of agriculture
A department of agriculture is a governmental or organizational body responsible for overseeing agricultural policies, supporting farmers, managing food safety and supply, and promoting sustainable use of natural resources in the agricultural sector.
-
E.
agricultural expert
An agricultural expert is a professional who applies scientific knowledge and practical experience to optimize crop and livestock production, manage natural resources sustainably, and advise stakeholders on best farming practices.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:17 p.m.