Triple
T15218732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleopatra Eurydice of Macedon |
E363706
|
entity |
| Predicate | childrenFate |
P67060
|
FINISHED |
| Object | children killed in dynastic struggle |
—
|
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: children killed in dynastic struggle | Statement: [Cleopatra Eurydice of Macedon, childrenFate, children killed in dynastic struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childrenFate Context triple: [Cleopatra Eurydice of Macedon, childrenFate, children killed in dynastic struggle]
-
A.
fateOfChild
chosen
Indicates the outcome or destiny that ultimately befalls a child as a result of certain circumstances, actions, or events.
-
B.
childInMyth
Indicates that one entity is described or portrayed as the child (offspring) of another entity within a mythological or legendary context.
-
C.
children
Indicates that one entity is the offspring or direct descendant of another entity.
-
D.
childInStory
Indicates that one entity is a child character who appears within the narrative context of the other entity (a story).
-
E.
childDuring
Indicates that one entity is the child of another specifically during a given time interval or temporal context.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007709d3881908384f0fe1e0218d0 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.