Triple
T24712375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amílcar Cabral |
E612064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agrarian engineer |
C1647
|
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: agrarian engineer Context triple: [Amílcar Cabral, instanceOf, agrarian engineer]
-
A.
agricultural engineering faculty
An agricultural engineering faculty is a group of academic staff specializing in the application of engineering principles to agricultural production, resource management, and related technologies within a higher education institution.
-
B.
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.
-
C.
agricultural expert
chosen
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.
-
D.
agricultural infrastructure
Agricultural infrastructure comprises the physical and organizational systems—such as irrigation networks, storage facilities, transportation, and processing plants—that support the efficient production, handling, and distribution of agricultural goods.
-
E.
civil engineer
A civil engineer is a professional who designs, constructs, and maintains infrastructure projects such as roads, bridges, buildings, and water systems to ensure safety, functionality, and sustainability.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 3:25 a.m.