Triple
T11413242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | archaeological area of Gela |
E270424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek archaeological site |
C24409
|
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 Greek archaeological site Context triple: [archaeological area of Gela, instanceOf, ancient Greek archaeological site]
-
A.
ancient Greek sanctuary
An ancient Greek sanctuary is a sacred precinct dedicated to one or more deities, typically containing temples, altars, votive offerings, and ritual spaces where religious ceremonies, festivals, and oracles took place.
-
B.
ancient village site
chosen
An ancient village site is an archaeological location preserving the remains of a past community’s dwellings, activity areas, and material culture, offering evidence of its social, economic, and environmental history.
-
C.
ancient sanctuary
An ancient sanctuary is a sacred, often secluded place dedicated to worship, ritual, or protection, typically imbued with religious or spiritual significance by past civilizations.
-
D.
Urartian archaeological site
An Urartian archaeological site is a location containing the material remains—such as fortresses, temples, settlements, and artifacts—of the Iron Age kingdom of Urartu, offering evidence of its political, economic, and religious life.
-
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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:34 p.m.