Triple
T20963920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uskudama |
E516317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Thracian settlement |
C43014
|
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 Thracian settlement Context triple: [Uskudama, instanceOf, ancient Thracian settlement]
-
A.
Thracian settlement
chosen
A Thracian settlement is an ancient community or habitation site established and occupied by the Thracian people, typically characterized by fortified structures, distinctive material culture, and strategic locations in the Balkans.
-
B.
Greco-Roman settlement
A Greco-Roman settlement is a community or town established or influenced by ancient Greek and Roman cultures, characterized by their architectural styles, urban planning, social structures, and economic activities.
-
C.
ancient village site
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.
-
D.
Aegean settlement
An Aegean settlement is a community or habitation site located in the Aegean region, typically characterized by its maritime connections, regional architecture, and cultural practices tied to the ancient civilizations surrounding the Aegean Sea.
-
E.
Mycenaean settlement
A Mycenaean settlement is a Late Bronze Age Aegean habitation site characterized by fortified architecture, palatial or administrative centers, and associated domestic, economic, and ritual structures reflecting Mycenaean social and political organization.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:32 p.m.