Triple
T16582068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onitsha Main Market |
E402858
|
entity |
| Predicate | hasTypeOfTrade |
P114890
|
FINISHED |
| Object | wholesale trade |
—
|
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: wholesale trade | Statement: [Onitsha Main Market, hasTypeOfTrade, wholesale trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfTrade Context triple: [Onitsha Main Market, hasTypeOfTrade, wholesale trade]
-
A.
typeOfTrading
chosen
Indicates a relationship where one entity specifies the kind or category of trading activity associated with another entity.
-
B.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
C.
supportsTradingType
Indicates that one entity enables, allows, or is compatible with a specified type or mode of trading.
-
D.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
E.
hasTradeCharacteristic
Indicates that an entity possesses a specific trade-related attribute, quality, or feature.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35998371c8190936dcdaab5ca7e21 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.