Triple
T30310079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlement de la Fédération Wallonie-Bruxelles |
E770897
|
entity |
| Predicate | typeOfActItAdopts |
P144132
|
FINISHED |
| Object | decree |
—
|
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: decree | Statement: [Parlement de la Fédération Wallonie-Bruxelles, typeOfActItAdopts, decree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfActItAdopts Context triple: [Parlement de la Fédération Wallonie-Bruxelles, typeOfActItAdopts, decree]
-
A.
natureOfAct
chosen
Indicates the inherent character or type of an action, describing what kind of act it is in terms of its qualities or legal/moral classification.
-
B.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
C.
actsFor
Indicates that one entity performs actions or exercises authority on behalf of another entity.
-
D.
implementsAct
Indicates that one entity carries out, executes, or puts into effect a specified act, plan, or directive associated with another entity.
-
E.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: April 29, 2026, 7:50 p.m.