Triple
T22620268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prokonnesos |
E558256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement in classical antiquity |
C36651
|
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: settlement in classical antiquity Context triple: [Prokonnesos, instanceOf, settlement in classical antiquity]
-
A.
settlement in ancient Italy
A settlement in ancient Italy is a populated place such as a village, town, or city that existed on the Italian peninsula during antiquity, characterized by its social organization, infrastructure, and interaction with surrounding communities and cultures.
-
B.
settlement in Greece
A settlement in Greece is a populated place, such as a village, town, or small community, recognized as an administrative or geographic unit within the country.
-
C.
Greco-Roman settlement
chosen
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.
-
D.
heritage of classical antiquity
The heritage of classical antiquity encompasses the enduring cultural, intellectual, artistic, and political legacies of ancient Greece and Rome that have profoundly shaped subsequent civilizations, especially in Europe and the Western world.
-
E.
history of the ancient world
The history of the ancient world examines the civilizations, cultures, events, and interactions of human societies from the earliest recorded times to the fall of the Western Roman Empire.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3 p.m.