Triple
T16765081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agia Triada |
E407442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archaeological site in Greece |
C2556
|
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: archaeological site in Greece Context triple: [Agia Triada, instanceOf, archaeological site in Greece]
-
A.
ancient Greek sanctuary
chosen
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.
village in Greece
A village in Greece is a small, traditionally structured rural settlement characterized by close-knit community life, local agriculture or tourism-based economy, and architecture reflecting Greek cultural and historical heritage.
-
C.
city in Greece
A city in Greece is an urban settlement within the national territory of Greece, characterized by a concentrated population, local governance structures, and economic, cultural, and social activities that serve its surrounding region.
-
D.
historical region of Greece
A historical region of Greece is a geographically defined area within the Greek world that is recognized for its distinct cultural, political, or historical identity during a specific period of the past.
-
E.
archaeological site in Mexico
An archaeological site in Mexico is a location where physical remains of past human activity—such as structures, artifacts, and cultural features—have been preserved and studied to understand the region’s historical and pre-Hispanic civilizations.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.