Triple
T35814356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purchase of Cyprus from Richard I of England |
E1035314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval transaction |
C65599
|
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 transaction Context triple: [Purchase of Cyprus from Richard I of England, instanceOf, medieval transaction]
-
A.
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.
-
B.
medieval marketplace
A medieval marketplace is a bustling open-air trading hub where merchants, peasants, and travelers gather to buy, sell, and barter goods amid lively sounds, vivid smells, and the backdrop of town life.
-
C.
medieval currency
Medieval currency encompasses the diverse coins, bullion, and sometimes barter-based units of value used in Europe and neighboring regions during the Middle Ages, reflecting complex systems of trade, authority, and economic hierarchy.
-
D.
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.
-
E.
medieval march
A medieval march is a border territory or frontier region of a kingdom or empire, governed by a margrave or similar official, established to defend against external threats and manage cross-border relations.
- F. None of above. chosen
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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.