Triple
T5938626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellanodikai |
E132108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek officials |
C19605
|
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 officials Context triple: [Hellanodikai, instanceOf, ancient Greek officials]
-
A.
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.
-
B.
ancient Athenian politician
An ancient Athenian politician was a public figure who participated in the governance and decision-making of the city-state of Athens, often through the Assembly, councils, and law courts, influencing policy, law, and civic life.
-
C.
Athenian politician
An Athenian politician is a public figure in ancient Athens who participates in the city-state’s democratic processes by proposing laws, debating policy, and influencing civic decision-making in the Assembly and other political institutions.
-
D.
Byzantine official
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
-
E.
Theban statesman
A Theban statesman is a political leader or public official from the ancient Greek city of Thebes who shaped its domestic policies, military strategies, and diplomatic relations within the Greek world.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.