Triple
T7222023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wales Act 1978 |
E150281
|
entity |
| Predicate | resultingEffect |
P53074
|
FINISHED |
| Object | Act not brought into force |
—
|
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: Act not brought into force | Statement: [Wales Act 1978, resultingEffect, Act not brought into force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultingEffect Context triple: [Wales Act 1978, resultingEffect, Act not brought into force]
-
A.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
B.
sideEffect
Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
-
C.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
D.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
E.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b42c5c81908c405f161c35ffb4 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:54 p.m.