Triple
T32302185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riksdag of Sweden |
E825265
|
entity |
| Predicate | receivesAnnualReportFrom |
P146872
|
FINISHED |
| Object | Sveriges Riksbank |
—
|
NE NERFINISHED |
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: Sveriges Riksbank | Statement: [Riksdag of Sweden, receivesAnnualReportFrom, Sveriges Riksbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesAnnualReportFrom Context triple: [Riksdag of Sweden, receivesAnnualReportFrom, Sveriges Riksbank]
-
A.
hasAnnualReportForm
Indicates that an entity is associated with a specific form used for its annual report.
-
B.
requiresAnnualFinancialReports
chosen
Indicates that one entity is obligated to provide annual financial reports to another entity or authority.
-
C.
isAnnualMessageOf
Indicates a relationship where a message is designated as the recurring yearly (annual) message associated with a particular entity or event.
-
D.
annualFrom
Indicates that something recurs or is calculated on a yearly basis starting from a specified point in time.
-
E.
hasAnnualList
Indicates that an entity maintains or is associated with a list that is updated or issued on an annual basis.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 12:45 a.m.