Triple
T18075775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filitosa |
E432548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | megalithic site |
C39792
|
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: megalithic site Context triple: [Filitosa, instanceOf, megalithic site]
-
A.
megalithic jar site
A megalithic jar site is an archaeological landscape characterized by the presence of large, carved stone jars, often arranged in groups, whose original function is typically associated with ancient ritual, funerary, or storage practices.
-
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.
nuragic archaeological site
A nuragic archaeological site is a prehistoric complex in Sardinia characterized by stone towers (nuraghi), villages, tombs, and ritual structures built by the Nuragic civilization between the Bronze and Iron Ages.
-
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.
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.
- F. None of above. chosen
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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.