Triple
T3628502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peloponnesian League |
E76897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek military alliance |
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 military alliance Context triple: [Peloponnesian League, instanceOf, ancient Greek military alliance]
-
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.
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.
-
C.
Catholic military alliance
A Catholic military alliance is a coalition of armed forces from predominantly Catholic states or groups, formed to defend shared religious, political, or territorial interests under a common Catholic identity.
-
D.
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.
-
E.
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.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.