Triple
T18449791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Leopoldowna |
E450748
|
entity |
| Predicate | cause of loss of power |
P52786
|
FINISHED |
| Object | coup d'état of 1741 |
—
|
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: coup d'état of 1741 | Statement: [Anna Leopoldowna, cause of loss of power, coup d'état of 1741]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cause of loss of power Context triple: [Anna Leopoldowna, cause of loss of power, coup d'état of 1741]
-
A.
reasonForLossOfPower
chosen
Indicates the cause or circumstance that led to a loss of power or authority.
-
B.
lossOfPower
Indicates that an entity experiences a reduction or complete removal of its ability to exert control, influence, or operational capability.
-
C.
causedLossOf
Indicates that one entity brought about or was responsible for another entity experiencing a loss.
-
D.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
E.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5264748dc8190984501af3e4b2036 |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.