Triple
T32302192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riksdag of Sweden |
E825265
|
entity |
| Predicate | definesProfitAllocationRulesFor |
P8188
|
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, definesProfitAllocationRulesFor, Sveriges Riksbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesProfitAllocationRulesFor Context triple: [Riksdag of Sweden, definesProfitAllocationRulesFor, Sveriges Riksbank]
-
A.
setsRulesFor
chosen
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
B.
allocatesAccordingTo
Indicates that one entity distributes or assigns resources, tasks, or responsibilities to others based on a specified rule, criterion, or plan.
-
C.
settingOfRule
Indicates the contextual environment, domain, or circumstances within which a particular rule is defined and intended to apply.
-
D.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
E.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
- 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_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 12:45 a.m.