Triple
T19716820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gortynia (Bottiaea) |
E473498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Macedonian city |
C17558
|
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 Macedonian city Context triple: [Gortynia (Bottiaea), instanceOf, ancient Macedonian city]
-
A.
Phrygian city
A Phrygian city is an ancient urban settlement located in the historical region of Phrygia in central Anatolia, characterized by its distinctive rock-cut architecture, religious monuments, and role in the Phrygian kingdom’s political and cultural life.
-
B.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
C.
ancient port city
An ancient port city is a historical urban center located on a coast or navigable waterway that served as a hub for maritime trade, cultural exchange, and strategic defense.
-
D.
ancient Greek colony
An ancient Greek colony is a settlement established by a Greek city-state in a foreign territory, maintaining political, cultural, and religious ties with its mother city while serving as a hub for trade, resource extraction, and territorial expansion.
-
E.
city in Greece
chosen
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.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.