Triple
T19617544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burghers of Plzeň |
E470907
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval urban community |
C9063
|
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 urban community Context triple: [Burghers of Plzeň, instanceOf, medieval urban community]
-
A.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
-
B.
medieval city
chosen
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
-
C.
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.
-
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 capital
A medieval capital is the carved topmost element of a column or pillar in Middle Ages architecture, often richly decorated with foliage, figures, or symbolic motifs to transition between the shaft and the structure it supports.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.