Triple
T28225531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | necropolis of Baza |
E711574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iberian archaeological site |
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: Iberian archaeological site Context triple: [necropolis of Baza, instanceOf, Iberian archaeological site]
-
A.
cultural heritage site in Spain
A cultural heritage site in Spain is a legally recognized place, structure, or landscape of historical, artistic, architectural, archaeological, or ethnographic significance that reflects the country’s diverse cultural legacy and is protected for its preservation and public appreciation.
-
B.
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.
-
C.
pre-Columbian site
A pre-Columbian site is an archaeological location in the Americas that preserves evidence of human activity and cultures that existed before the arrival of Christopher Columbus in 1492.
-
D.
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.
-
E.
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.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:49 p.m.