Triple
T30030016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LL Convention |
E762988
|
entity |
| Predicate | typeOfSafetyRegulation |
P14058
|
FINISHED |
| Object | construction-related safety regulation |
—
|
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-related safety regulation | Statement: [LL Convention, typeOfSafetyRegulation, construction-related safety regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSafetyRegulation Context triple: [LL Convention, typeOfSafetyRegulation, construction-related safety regulation]
-
A.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
B.
regulatoryType
chosen
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
C.
safetyStandardLevel
Indicates the degree or tier of safety requirements or protections that apply to an entity or activity.
-
D.
categoryForRegulation
Indicates that something is assigned to a specific regulatory category or classification for the purposes of applying rules or controls.
-
E.
safetyRegulationEffect
Indicates how a safety regulation influences or changes the conditions, behaviors, or outcomes associated with the regulated entities.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 29, 2026, 6:49 p.m.