Triple
T17204726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuraghe Losa |
E417569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bronze Age structure |
C27632
|
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: Bronze Age structure Context triple: [Nuraghe Losa, instanceOf, Bronze Age structure]
-
A.
ancient structure
chosen
An ancient structure is a man-made construction from antiquity, such as temples, fortifications, or monuments, that reflects the architectural techniques, cultural values, and historical context of its originating civilization.
-
B.
Iron Age site
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.
-
C.
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.
-
D.
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.
-
E.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:38 a.m.