Triple
T19086835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faculty of Agricultural Engineering |
E467171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agricultural engineering faculty |
C40986
|
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: agricultural engineering faculty Context triple: [Faculty of Agricultural Engineering, instanceOf, agricultural engineering faculty]
-
A.
agricultural engineering department
An agricultural engineering department is an academic and research unit that applies engineering principles to improve agricultural production, processing, and resource management systems.
-
B.
faculty of science and engineering
The faculty of science and engineering is an academic division within a university that focuses on education and research in scientific and technological disciplines, including natural sciences, mathematics, and various branches of engineering.
-
C.
college of engineering
A college of engineering is an academic division within a university that offers specialized education and research programs in various engineering disciplines, preparing students for professional engineering careers and technological innovation.
-
D.
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.
-
E.
engineering institute
An engineering institute is an educational and research organization dedicated to teaching, advancing, and applying engineering principles and technologies across various specialized fields.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.