Triple
T32302163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riksdag of Sweden |
E825265
|
entity |
| Predicate | setsStatutoryTasksFor |
P67335
|
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, setsStatutoryTasksFor, Sveriges Riksbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsStatutoryTasksFor Context triple: [Riksdag of Sweden, setsStatutoryTasksFor, Sveriges Riksbank]
-
A.
setTaskFor
Indicates assigning or configuring a specific task to be carried out for a particular entity or context.
-
B.
statutoryDuty
Indicates that an entity is legally obligated by statute to perform, refrain from, or ensure a specific action or condition.
-
C.
setsObligationsFor
Indicates that one party establishes duties, responsibilities, or required actions that another party is bound to fulfill.
-
D.
definesTasksOf
chosen
Indicates that one entity specifies or establishes the tasks, duties, or responsibilities assigned to another entity.
-
E.
isStatutory
Indicates that something exists, applies, or is defined by virtue of formal law or statute rather than by custom, contract, or other sources.
- 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_69f6bd7784908190a3e4da8c3fb84e5e |
completed | May 3, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.