Triple
T3591427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirty Years' Peace |
E76033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek treaty |
C13422
|
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 treaty Context triple: [Thirty Years' Peace, instanceOf, ancient Greek treaty]
-
A.
ancient Greek alliance
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.
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.
-
C.
ancient Greek
An ancient Greek is a person from the civilizations of classical Greece, typically characterized by participation in city-state life, polytheistic religion, and contributions to early Western philosophy, art, and politics.
-
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.
Athenian legal proceeding
An Athenian legal proceeding is a public, citizen-driven trial in classical Athens where litigants present their own cases before a large jury of fellow citizens who decide verdict and penalty without professional judges or lawyers.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.