Triple
T2218422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigismund III Vasa |
E48083
|
entity |
| Predicate | causeOfLossOfSwedishCrown |
P15555
|
FINISHED |
| Object | deposition by the Riksdag of the Estates |
—
|
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: deposition by the Riksdag of the Estates | Statement: [Sigismund III Vasa, causeOfLossOfSwedishCrown, deposition by the Riksdag of the Estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfLossOfSwedishCrown Context triple: [Sigismund III Vasa, causeOfLossOfSwedishCrown, deposition by the Riksdag of the Estates]
-
A.
kingOfSwedenPresent
Indicates that the current reigning monarch of Sweden is present at a specified place, event, or context.
-
B.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
endOfReignReason
chosen
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
strengthSweden
Indicates the level or degree of strength associated with Sweden in a given 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc011d50c8190b1c375cc633f8189 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.