Triple
T14857756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kankan |
E349403
|
entity |
| Predicate | historicTradeGoods |
P34774
|
FINISHED |
| Object | kolanuts |
—
|
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: kolanuts | Statement: [Kankan, historicTradeGoods, kolanuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicTradeGoods Context triple: [Kankan, historicTradeGoods, kolanuts]
-
A.
historicTradeRole
Indicates that an entity historically functioned as a significant participant or hub in trade or commercial exchange.
-
B.
historicallyStoredGoods
chosen
Indicates that an entity has previously stored certain goods at some time in the past.
-
C.
historicalPeriodOfIntenseTrade
Indicates a time span characterized by unusually high levels of trade activity between parties or regions.
-
D.
tradeItemsHistorically
Indicates that the entities have engaged in trading items with each other at some point in the past.
-
E.
usedForTradeBetween
Indicates that something serves as a medium, instrument, or basis for trade or exchange between two or more parties.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44458ec8190be295a95f5daab14 |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.