Triple
T31996590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgar merchants |
E817008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval merchants |
C47151
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medieval merchants Context triple: [Bulgar merchants, instanceOf, medieval merchants]
-
A.
historical merchants
chosen
Historical merchants were individuals or groups engaged in the long-distance or local trade of goods and services, often acting as key intermediaries who connected different regions, cultures, and economies throughout history.
-
B.
medieval trading network
A medieval trading network is an interconnected system of routes, markets, and merchants that facilitated the exchange of goods, money, and information across regions during the Middle Ages.
-
C.
medieval trading colony
A medieval trading colony is a distant settlement established and controlled by a city or state to facilitate long-distance commerce, resource extraction, and cultural exchange through permanent mercantile presence.
-
D.
merchant dynasty
A merchant dynasty is a powerful family or lineage whose wealth, influence, and social status are built and sustained over generations through large-scale trade and commercial enterprises.
-
E.
merchant guild
A merchant guild is an organized association of traders and businesspeople who collaborate to regulate commerce, protect mutual interests, and maintain standards within a particular market or region.
- F. None of above.
Provenance (1 batch)
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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:14 a.m.