Triple
T18070014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heracles of Macedon |
E432399
|
entity |
| Predicate | claimToThroneBasedOn |
P7973
|
FINISHED |
| Object | being son of Alexander the Great |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: being son of Alexander the Great | Statement: [Heracles of Macedon, claimToThroneBasedOn, being son of Alexander the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimToThroneBasedOn Context triple: [Heracles of Macedon, claimToThroneBasedOn, being son of Alexander the Great]
-
A.
claimedThroneAfter
Indicates that one entity assumed or asserted the right to a throne following the reign, death, or removal of another entity.
-
B.
reignClaim
Indicates a claim or assertion by an entity that it has the right to rule or hold sovereign authority over a domain or people.
-
C.
kingdomClaimed
Indicates that an entity has asserted ownership, control, or sovereign authority over a particular kingdom.
-
D.
dynasticClaim
chosen
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
E.
claimedTitle
Indicates that an entity asserts or declares possession of a particular title or rank.
- F. None of above.
Provenance (3 batches)
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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cced29fc81908e87b4f1990fa0d8 |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.