Triple
T6770100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Welsh devolution referendum |
E155020
|
entity |
| Predicate | devolvedAreas |
P73180
|
FINISHED |
| Object | education |
—
|
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: education | Statement: [2011 Welsh devolution referendum, devolvedAreas, education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devolvedAreas Context triple: [2011 Welsh devolution referendum, devolvedAreas, education]
-
A.
devolutionTo
Indicates the transfer or delegation of authority, responsibility, or rights from one entity or level to another, typically lower or more localized, entity.
-
B.
isDevolvedOffice
Indicates that an office or authority has been transferred from a central government to a regional or local governing body.
-
C.
numberOfAreaCouncils
Indicates the total count of area councils associated with a given entity.
-
D.
electoralConstituencies
Indicates a relationship where a geographic or political area is divided into specific electoral constituencies used for representation or voting.
-
E.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2347fb48190a44c03317b5ecfd7 |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:13 p.m.