Triple
T19416487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road Traffic Act 1934 (United Kingdom) |
E485729
|
entity |
| Predicate | policyResponseTo |
P135791
|
FINISHED |
| Object | public concern about road deaths |
—
|
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: public concern about road deaths | Statement: [Road Traffic Act 1934 (United Kingdom), policyResponseTo, public concern about road deaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyResponseTo Context triple: [Road Traffic Act 1934 (United Kingdom), policyResponseTo, public concern about road deaths]
-
A.
policyElement
Indicates that something is a component or constituent part of a broader policy.
-
B.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
C.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
D.
policySetBy
Indicates that a particular policy is established, defined, or determined by a specific entity or authority.
-
E.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af9c8fc81909860de10b6720207 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.