Triple
T10854624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scidrus |
E256239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek colonial settlement |
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 colonial settlement Context triple: [Scidrus, instanceOf, ancient Greek colonial settlement]
-
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.
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.
-
C.
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.
-
D.
Minoan settlement
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.
-
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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.