Triple
T30829004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business for Britain |
E785157
|
entity |
| Predicate | stanceOnEURegulation |
P171601
|
FINISHED |
| Object | critical |
—
|
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: critical | Statement: [Business for Britain, stanceOnEURegulation, critical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stanceOnEURegulation Context triple: [Business for Britain, stanceOnEURegulation, critical]
-
A.
usesEuropeanUnionDSTRules
Indicates that the action or process is governed by, or conforms to, the European Union’s Digital Services Act (DSA) rules and requirements.
-
B.
followsEuropeanUnionDSTRules
Indicates that an entity’s actions, processes, or services comply with the regulatory requirements set out in the European Union’s Digital Services Act (DSA) rules.
-
C.
classificationByEuropeanUnion
Indicates the categorization or regulatory status assigned to an entity according to European Union classification systems or standards.
-
D.
relationshipWithEU
Indicates the nature or status of an entity’s formal or informal relationship with the European Union.
-
E.
wasApprovedInEUOn
Indicates that an entity received official approval within the European Union on a specified date.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:44 p.m.