Triple
T22513766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corlea Trackway |
E556588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iron Age monument |
C25917
|
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: Iron Age monument Context triple: [Corlea Trackway, instanceOf, Iron Age monument]
-
A.
Iron Age site
chosen
An Iron Age site is an archaeological location containing material remains, features, and structures dating to the period when iron became the dominant material for tools and weapons, typically characterized by specific regional cultural, technological, and settlement patterns.
-
B.
Neolithic henge
A Neolithic henge is a prehistoric earthwork monument characterized by a circular or oval bank and internal ditch, often associated with ritual, ceremonial, or astronomical functions.
-
C.
Anglo-Saxon burial mound
An Anglo-Saxon burial mound is an earthen or stone-built barrow constructed in early medieval England to cover and mark the grave of an individual, often accompanied by grave goods and sometimes elaborate funerary structures.
-
D.
prehistoric platform mound
A prehistoric platform mound is a human-made earthen or stone elevation constructed in ancient times, typically serving as a base for structures, ceremonies, or elite residences within a broader cultural or ritual landscape.
-
E.
megalithic site
A megalithic site is a location featuring large stone structures or arrangements, typically constructed in prehistoric times for ceremonial, religious, or funerary purposes.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.