Triple
T11514490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health Hazard Evaluation Program |
E272995
|
entity |
| Predicate | requestableBy |
P67728
|
FINISHED |
| Object | employers |
—
|
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: employers | Statement: [Health Hazard Evaluation Program, requestableBy, employers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestableBy Context triple: [Health Hazard Evaluation Program, requestableBy, employers]
-
A.
requestedBy
Indicates that one entity has made a request for something to be done, provided, or obtained by another entity.
-
B.
requisitionedBy
Indicates that something has been formally requested or claimed for official use by a particular agent or authority.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requestsCooperationWith
Indicates that one entity asks another entity to collaborate or assist in achieving a task, goal, or outcome.
-
E.
canBePetitionedBy
chosen
Indicates that an entity is eligible to receive formal petitions, requests, or appeals from another 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db8bf9c8190820c289e6b0c3873 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.