Triple
T20579610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vicars’ Close, Wells |
E505316
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval residential street |
C1088
|
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 residential street Context triple: [Vicars’ Close, Wells, instanceOf, medieval residential street]
-
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
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.
ancient Roman street
An ancient Roman street is a paved public thoroughfare, typically constructed of stone blocks with raised sidewalks, drainage systems, and often lined with shops, houses, and public buildings, facilitating movement, trade, and social interaction within Roman cities.
-
D.
street
chosen
A street is a public thoroughfare in an urban or suburban area, typically bordered by buildings, that facilitates vehicular and pedestrian movement and often supports various social and commercial activities.
-
E.
pedestrian village
A pedestrian village is a compact, human-scaled settlement designed so that daily needs can be met on foot, with car access minimized or restricted to prioritize walkability, public spaces, and community interaction.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:39 a.m.