Triple
T11892392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thirty Tyrants |
E282947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Athenian government |
C10510
|
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: Athenian government Context triple: [Thirty Tyrants, instanceOf, Athenian government]
-
A.
Athenian political institution
chosen
An Athenian political institution is a formal structure or body within ancient Athens’ democratic system that organized, regulated, and executed public decision-making, governance, and civic participation.
-
B.
Greek constitution
The Greek constitution is the fundamental legal framework that defines the structure, powers, and functions of the Greek state, guarantees citizens' rights and freedoms, and regulates the relationship between public authorities and individuals.
-
C.
ancient Greek officials
Ancient Greek officials were public functionaries appointed or elected within the city-states to administer civic, religious, military, and judicial duties according to local laws and customs.
-
D.
Athenian public works program
Athenian public works program: A state-sponsored initiative in classical Athens that funded large-scale construction, infrastructure, and artistic projects—often employing citizens and metics—to enhance civic life, display communal wealth and power, and provide economic support.
-
E.
classical Athenian politician
A classical Athenian politician is a public figure of ancient Athens who engaged in the city’s democratic processes by proposing laws, debating in the Assembly, and influencing civic policy and public opinion.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.