Triple
T30926629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ráith na Seanadh |
E787874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient earthwork enclosure |
C29588
|
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: ancient earthwork enclosure Context triple: [Ráith na Seanadh, instanceOf, ancient earthwork enclosure]
-
A.
Neolithic henge
chosen
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.
-
B.
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.
-
C.
archaeological mound
An archaeological mound is an artificial or modified natural elevation of earth, stone, or debris created by past human activity, often containing buried cultural materials and serving as a key source of information about ancient societies.
-
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.
earthen building complex
An earthen building complex is a group of interconnected or closely related structures primarily constructed from earth-based materials such as rammed earth, adobe, or cob, forming a cohesive architectural ensemble.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.