Triple
T9856955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic Old Town of Lublin |
E239611
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval urban area |
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 area Context triple: [historic Old Town of Lublin, instanceOf, medieval urban area]
-
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.
medieval city wall
A medieval city wall is a fortified defensive structure encircling a town or city, typically built of stone with towers, gates, and battlements to protect inhabitants from external threats.
-
D.
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.
-
E.
medieval castle
A medieval castle is a fortified stone stronghold featuring defensive walls, towers, and a keep, designed to protect its inhabitants and assert the power of its lord.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:35 p.m.