Triple
T3209340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilorin |
E67240
|
entity |
| Predicate | regionEconomicActivity |
P1099
|
FINISHED |
| Object | commerce |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: commerce | Statement: [Ilorin, regionEconomicActivity, commerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionEconomicActivity Context triple: [Ilorin, regionEconomicActivity, commerce]
-
A.
regionalEconomyType
Indicates the type or classification of an economy associated with a specific region.
-
B.
economicImpactRegion
Indicates the region or geographic area that experiences or is affected by a particular economic impact.
-
C.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
D.
hasEconomicActivity
chosen
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
E.
hasEconomicActivityLevel
Indicates the degree or intensity of economic activity associated with an entity, such as its level of production, trade, or financial transactions.
- F. None of above.
Provenance (3 batches)
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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaab701c48190b91404ab416f7ce3 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.