Triple
T30611608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midi-job |
E779192
|
entity |
| Predicate | introducedForPolicyGoal |
P14666
|
FINISHED |
| Object | to combat precarious employment |
—
|
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: to combat precarious employment | Statement: [Midi-job, introducedForPolicyGoal, to combat precarious employment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForPolicyGoal Context triple: [Midi-job, introducedForPolicyGoal, to combat precarious employment]
-
A.
hasPolicyGoal
chosen
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
B.
supportsPolicyGoal
Indicates that one entity’s actions, positions, or characteristics help advance, uphold, or contribute to achieving a specified policy goal.
-
C.
policyIntroduced
Indicates that a specific policy has been formally brought into effect or announced by an authority or organization.
-
D.
targetedPolicy
Indicates that a policy is specifically directed at, or designed to affect, a particular subset of entities rather than applying broadly.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 8:26 p.m.