Triple
T18195950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amnisos |
E435662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Minoan harbor settlement |
C26465
|
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 Minoan harbor settlement Context triple: [Amnisos, instanceOf, ancient Minoan harbor settlement]
-
A.
Minoan settlement
chosen
A Minoan settlement is a Bronze Age Cretan habitation site characterized by clustered domestic, religious, and sometimes administrative structures that reflect the social, economic, and cultural organization of Minoan society.
-
B.
Minoan town
A Minoan town is an ancient urban settlement from Bronze Age Crete characterized by complex architecture, advanced infrastructure, and a central role in the island’s economic, social, and religious life.
-
C.
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.
-
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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:31 a.m.