Triple
T9486664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Saharan trade routes |
E228779
|
entity |
| Predicate | mainCommodityTraded |
P73592
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Trans-Saharan trade routes, mainCommodityTraded, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCommodityTraded Context triple: [Trans-Saharan trade routes, mainCommodityTraded, gold]
-
A.
majorTradeType
Indicates the primary category or kind of trade activity that characterizes the relationship between the involved entities.
-
B.
commodityType
chosen
Indicates the classification of a good or product according to its type or category within a commodity system.
-
C.
commodityProduced
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
D.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
E.
importedCommodity
Indicates that a commodity has been brought into a country or region from abroad through import activities.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd8051303881909566126a2688e41c |
completed | April 1, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.