Triple
T1060922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleusis |
E22904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek city |
C4264
|
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 city Context triple: [Eleusis, instanceOf, ancient Greek city]
-
A.
ancient Greek colony
chosen
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.
-
B.
Mediterranean port city
A Mediterranean port city is a coastal urban center situated along the Mediterranean Sea that serves as a hub for maritime trade, cultural exchange, and tourism, often characterized by historic harbors, diverse architecture, and a mild climate.
-
C.
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.
-
D.
ancient Greek
An ancient Greek is a person from the civilizations of classical Greece, typically characterized by participation in city-state life, polytheistic religion, and contributions to early Western philosophy, art, and politics.
-
E.
ancient Greek war
Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.