Triple
T23377046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaeus (son of Seleucus I) |
E593635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic nobleman |
C19770
|
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 nobleman Context triple: [Achaeus (son of Seleucus I), instanceOf, Hellenistic nobleman]
-
A.
ancient Macedonian nobleman
An ancient Macedonian nobleman is a high-ranking member of Macedonian aristocracy who held land, military command, and political influence within the kingdom’s hierarchical social and governmental structure.
-
B.
Hellenistic-era monarch
A Hellenistic-era monarch is a ruler who governed one of the successor kingdoms to Alexander the Great’s empire, blending Greek political and cultural traditions with local customs across a diverse, often expansive territory.
-
C.
Greek aristocrat
chosen
A Greek aristocrat is a wealthy, high-status individual from ancient or modern Greece, typically belonging to a privileged landowning or politically influential family and embodying traditional cultural refinement and social power.
-
D.
Phoenician nobleman
A Phoenician nobleman is a high-ranking member of ancient Phoenician society who wields political, economic, and social influence through control of trade, land, and maritime enterprises.
-
E.
Roman aristocrat
A Roman aristocrat is a wealthy, high-status citizen of ancient Rome who wields political, social, and economic power through land ownership, patronage networks, and participation in public life.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:33 p.m.