Triple
T24404098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senedd electoral regions of Wales |
E615258
|
entity |
| Predicate | formerlyFor |
P146400
|
FINISHED |
| Object | National Assembly for Wales |
—
|
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: National Assembly for Wales | Statement: [Senedd electoral regions of Wales, formerlyFor, National Assembly for Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyFor Context triple: [Senedd electoral regions of Wales, formerlyFor, National Assembly for Wales]
-
A.
formerName
Indicates that an entity was previously known by a different name in the past.
-
B.
former
chosen
Indicates that an entity previously held a role, status, or relationship but no longer does so in the present.
-
C.
formerlyConfiguration
Indicates that one entity was previously configured or arranged in the state or setup represented by the other entity, but is no longer so.
-
D.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
-
E.
formerLabel
Indicates that an entity previously had a certain label or designation, but no longer holds it.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dcf7f4819094d2a3be163a5822 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.