Triple
T13492892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margilan |
E320679
|
entity |
| Predicate | tradeGoodsHistorical |
P14355
|
FINISHED |
| Object | silk |
—
|
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: silk | Statement: [Margilan, tradeGoodsHistorical, silk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeGoodsHistorical Context triple: [Margilan, tradeGoodsHistorical, silk]
-
A.
tradeItemsHistorically
Indicates that the entities have engaged in trading items with each other at some point in the past.
-
B.
historicallyStoredGoods
Indicates that an entity has previously stored certain goods at some time in the past.
-
C.
currencyHistorically
Indicates that one entity has served as the official or commonly used currency of another entity during some period in the past.
-
D.
historicalTradeDirection
Indicates the predominant directional flow of trade between entities during a specified historical period.
-
E.
keyHistoricalProduct
chosen
Indicates that the product played a significant or defining role in the historical development, identity, or evolution of the associated entity.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4c66008190b287e0551889d7c8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.