Triple
T34555353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangote Fertilizer |
E887187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fertilizer manufacturing company |
C48956
|
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: fertilizer manufacturing company Context triple: [Dangote Fertilizer, instanceOf, fertilizer manufacturing company]
-
A.
fertilizer manufacturer
chosen
A fertilizer manufacturer is a business entity that produces, blends, and packages nutrient-rich chemical or organic products designed to enhance soil fertility and support plant growth for agricultural, horticultural, or landscaping use.
-
B.
chemical industry company
A chemical industry company is an organization that researches, manufactures, and sells chemical substances and related products for use in industrial, commercial, and consumer applications.
-
C.
multinational chemical company
A multinational chemical company is a large, globally operating enterprise that researches, manufactures, and distributes a wide range of chemical products and materials across multiple industries and countries.
-
D.
manufacturing company
A manufacturing company is an organization that transforms raw materials or components into finished goods through industrial processes, machinery, and labor for sale to other businesses or consumers.
-
E.
controlled-environment agriculture company
A controlled-environment agriculture company designs, builds, and operates highly managed indoor or enclosed growing systems that optimize climate, lighting, water, and nutrients to produce consistent, high-quality crops year-round.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.