Triple
T14480497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermotimus of Clazomenae |
E359089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | person from Clazomenae |
C34833
|
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: person from Clazomenae Context triple: [Hermotimus of Clazomenae, instanceOf, person from Clazomenae]
-
A.
ruler of Halicarnassus
A ruler of Halicarnassus is a sovereign or governing authority who held political and military control over the ancient Greek-Carian city of Halicarnassus, overseeing its administration, defense, and regional influence.
-
B.
person from Tarentum
A person from Tarentum is an individual originating from or residing in the ancient Greek city of Tarentum (modern-day Taranto) in southern Italy.
-
C.
monarch of Pontus
A monarch of Pontus is the sovereign ruler of the ancient Hellenistic kingdom of Pontus, exercising supreme political, military, and religious authority over its territories along the southern coast of the Black Sea.
-
D.
king of Lydia
A king of Lydia is the sovereign ruler of the ancient Anatolian kingdom of Lydia, holding supreme political, military, and religious authority over its people and territories.
-
E.
King of Pergamon
A King of Pergamon was the sovereign ruler of the ancient Hellenistic kingdom of Pergamon in western Asia Minor, wielding political, military, and cultural authority over its territories and people.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.