Triple
T9454897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on Taxation |
E227989
|
entity |
| Predicate | decisionProcessStage |
P88265
|
FINISHED |
| Object | committee stage in the Riksdag legislative process |
—
|
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: committee stage in the Riksdag legislative process | Statement: [Committee on Taxation, decisionProcessStage, committee stage in the Riksdag legislative process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionProcessStage Context triple: [Committee on Taxation, decisionProcessStage, committee stage in the Riksdag legislative process]
-
A.
decisionPointFor
Indicates a point in a process or workflow at which a choice must be made that determines which subsequent path or outcome will follow.
-
B.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
-
C.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
D.
decisionSplit
Indicates that a single decision point branches into multiple alternative outcomes or paths.
-
E.
goalStage
Indicates the specific phase or step a goal is currently in within its overall progression or lifecycle.
- F. None of above. chosen
Provenance (4 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f8e2c388190a4c5ee6e6d5f2585 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:52 p.m.