Triple
T28586698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornish stannaries |
E723523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval economic institution |
C6688
|
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 economic institution Context triple: [Cornish stannaries, instanceOf, medieval economic institution]
-
A.
medieval institution
chosen
A medieval institution is an organized social, political, religious, or economic structure—such as the Church, feudal lordship, or guilds—that governed relationships, authority, and daily life in medieval society.
-
B.
economic institution
An economic institution is an established system of rules, organizations, and practices that structure the production, distribution, and consumption of goods and services within a society.
-
C.
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.
-
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.
early modern urban institution
An early modern urban institution is a formally organized body—such as a guild, court, municipal council, or charitable foundation—embedded in a city between roughly 1500 and 1800 that structured social, economic, political, or religious life through codified rules and recognized authority.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:18 a.m.