Triple
T31401133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | standing committee of the Riksdag |
E800997
|
entity |
| Predicate | isAdHoc |
P171832
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [standing committee of the Riksdag, isAdHoc, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdHoc Context triple: [standing committee of the Riksdag, isAdHoc, false]
-
A.
isADROf
Indicates a relationship where one entity serves as the Authorized Designated Responsible Officer (ADRO) for another entity, typically bearing formal oversight or accountability on its behalf.
-
B.
isAdaptive
Indicates that an entity can adjust or modify its behavior, structure, or response in reaction to changing conditions or inputs.
-
C.
isInvitational
Indicates that one entity extends or offers an invitation to another entity.
-
D.
isActually
Indicates that something is in fact a particular way or identity, often clarifying or correcting a previous or apparent understanding.
-
E.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 29, 2026, 9:19 p.m.