Triple
T4892640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directorate of Construction |
E109599
|
entity |
| Predicate | regulatorFor |
P4784
|
FINISHED |
| Object | construction employers covered by OSHA |
—
|
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: construction employers covered by OSHA | Statement: [Directorate of Construction, regulatorFor, construction employers covered by OSHA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatorFor Context triple: [Directorate of Construction, regulatorFor, construction employers covered by OSHA]
-
A.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
-
B.
regulatorEstablished
Indicates that an entity has formally created, instituted, or set up a regulatory body or authority.
-
C.
primaryRegulator
chosen
Indicates that one entity serves as the main controlling or governing authority over another entity or process.
-
D.
regulatesWith
Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
-
E.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.