Triple
T4925664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosmeston Medieval Village |
E110569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed medieval village |
C8110
|
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: reconstructed medieval village Context triple: [Cosmeston Medieval Village, instanceOf, reconstructed medieval village]
-
A.
reconstructed historic site
chosen
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
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.
historic village
A historic village is a small, preserved settlement that reflects the architecture, culture, and way of life of a particular past era.
-
D.
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.
-
E.
former village
A former village is a once-inhabited settlement that has lost its status or population as a village, often due to abandonment, depopulation, or administrative reclassification.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:30 p.m.