Triple
T9708450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gournia |
E234958
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minoan town |
C26466
|
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: Minoan town Context triple: [Gournia, instanceOf, Minoan town]
-
A.
Minoan palace complex
A Minoan palace complex is a large, multi-functional architectural center of Minoan civilization that integrated political, religious, economic, and residential activities within an elaborate, often labyrinthine layout.
-
B.
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.
-
C.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
-
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.
Phoenician colony
A Phoenician colony is a settlement established by the ancient maritime Phoenician civilization along foreign coasts for trade, resource extraction, and cultural expansion while maintaining ties to its founding city.
- F. None of above. chosen
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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.