Triple
T31036921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INAIL |
E790874
|
entity |
| Predicate | providesToEmployers |
P158397
|
FINISHED |
| Object | risk assessment support |
—
|
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: risk assessment support | Statement: [INAIL, providesToEmployers, risk assessment support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesToEmployers Context triple: [INAIL, providesToEmployers, risk assessment support]
-
A.
collegeEmployer
Indicates that a college or university is the employing institution of a given person or organization.
-
B.
employabilityFocus
Indicates that the primary emphasis is on enhancing or assessing an entity’s capacity to gain and maintain employment.
-
C.
employerOfGraduates
Indicates that an entity serves as the employing organization for individuals who have graduated from a particular institution or program.
-
D.
employersInclude
Indicates that a specified set or group of employers contains, as members, the employer or employers referenced by the other argument.
-
E.
employerService
chosen
Indicates that one entity provides employment-related services or functions to another entity, typically in the role of an employer.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 29, 2026, 8:59 p.m.