Triple
T14252777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megacles (through marriage) |
E353310
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Alcmaeonid family |
C24076
|
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: member of the Alcmaeonid family Context triple: [Megacles (through marriage), instanceOf, member of the Alcmaeonid family]
-
A.
member of the Deinomenid dynasty
A member of the Deinomenid dynasty is an individual belonging to the ruling family that controlled Syracuse and parts of Sicily in the early 5th century BCE, originating from the tyrant Gelon and his relatives.
-
B.
member of the Magonid dynasty
A member of the Magonid dynasty is an individual belonging to the powerful Carthaginian ruling family, active mainly in the 6th–4th centuries BCE, known for producing influential military and political leaders who shaped Carthage’s expansion and foreign policy.
-
C.
Athenian aristocrat
chosen
An Athenian aristocrat is a wealthy, land-owning citizen of ancient Athens who holds social prestige, political influence, and cultural authority within the city-state’s elite class.
-
D.
member of a political family
A member of a political family is an individual whose close relatives hold or have held public office, often benefiting from shared influence, name recognition, and established political networks.
-
E.
Athenian noblewoman
An Athenian noblewoman is an elite female citizen of ancient Athens, defined by her aristocratic birth, domestic authority, and role in managing household affairs and family alliances within a patriarchal city-state.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.