Triple
T31044018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Shantok Archeological District |
E791073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fortified village site |
C13727
|
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: fortified village site Context triple: [Fort Shantok Archeological District, instanceOf, fortified village site]
-
A.
ancient village site
An ancient village site is an archaeological location preserving the remains of a past community’s dwellings, activity areas, and material culture, offering evidence of its social, economic, and environmental history.
-
B.
fortified settlement
chosen
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
C.
fortified town
A fortified town is a settlement enclosed by defensive structures such as walls, towers, and gates, designed to protect its inhabitants and resources from external threats.
-
D.
Celtic oppidum
A Celtic oppidum is a large fortified Iron Age settlement, typically situated on elevated ground, that functioned as a regional center for trade, governance, and defense in Celtic societies.
-
E.
fortified building
A fortified building is a heavily constructed structure designed with defensive features such as thick walls, limited entry points, and protective battlements to resist attacks and provide security for its occupants.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.