Triple
T20640666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalcidian League |
E507211
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek political federation |
C10512
|
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 political federation Context triple: [Chalcidian League, instanceOf, ancient Greek political federation]
-
A.
ancient Greek alliance
chosen
An ancient Greek alliance is a formal coalition of independent city-states that coordinate their military, political, and sometimes economic actions for mutual defense or shared objectives.
-
B.
pair of ancient Greek city-states
A pair of ancient Greek city-states represents two independent polis communities considered together for comparison, interaction, alliance, or conflict within the broader context of classical Greek civilization.
-
C.
ancient republic
An ancient republic is a form of government in classical antiquity where political power is held by a body of citizens and their elected or appointed representatives, rather than by a monarch.
-
D.
Athenian-led coalition
An Athenian-led coalition is an alliance of city-states or political entities organized under the leadership and strategic direction of Athens to pursue shared military, political, or economic objectives.
-
E.
Spartan political institution
The Spartan political institution was a mixed constitution combining dual kingship, a council of elders (Gerousia), elected magistrates (Ephors), and an assembly of male citizens to maintain military discipline, social order, and oligarchic control.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:43 a.m.