Triple
T25789692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union Act 2011 |
E649515
|
entity |
| Predicate | statusAfterBrexit |
P101761
|
FINISHED |
| Object | largely repealed |
—
|
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: largely repealed | Statement: [European Union Act 2011, statusAfterBrexit, largely repealed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterBrexit Context triple: [European Union Act 2011, statusAfterBrexit, largely repealed]
-
A.
positionOnBrexit
Indicates a stance or viewpoint an entity holds regarding the United Kingdom’s decision to leave the European Union (Brexit).
-
B.
resultEffectOnBrexit
Indicates the effect or impact that a particular result has on Brexit.
-
C.
postBrexitStatus
chosen
Indicates the status or condition of an entity specifically in the context of the period or circumstances following Brexit.
-
D.
brexitPhase
Indicates the specific stage or phase a process, negotiation, or situation is in within the broader context of Brexit.
-
E.
postBrexitFramework
Indicates the regulatory, legal, or institutional arrangements that govern relationships and operations after the United Kingdom’s exit from the European Union.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 22, 2026, 5:58 a.m.