Triple
T19828100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy son of Dorymenes |
E476381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic military officer |
C14764
|
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: Hellenistic military officer Context triple: [Ptolemy son of Dorymenes, instanceOf, Hellenistic military officer]
-
A.
Seleucid general
A Seleucid general is a high-ranking military commander serving the Hellenistic Seleucid Empire, responsible for leading armies, managing campaigns, and maintaining imperial control over diverse and often contested territories.
-
B.
Athenian general
An Athenian general is a high-ranking military and political leader of ancient Athens responsible for commanding armies, planning campaigns, and often influencing civic decision-making.
-
C.
Phocian general
A Phocian general is a high-ranking military commander from the ancient Greek region of Phocis, responsible for leading its armies in warfare and strategic defense.
-
D.
Syracusan general
A Syracusan general is a high-ranking military commander from the ancient Greek city-state of Syracuse, responsible for leading its armies in warfare and overseeing strategic defense and expansion.
-
E.
ancient Greek military leader
chosen
An ancient Greek military leader is a high-ranking commander responsible for organizing, directing, and strategizing the actions of Greek city-state or coalition forces in warfare.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.