Triple
T30358618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathode Ray Tube |
E772210
|
entity |
| Predicate | isRegulatedFor |
P34837
|
FINISHED |
| Object | radiation safety |
—
|
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: radiation safety | Statement: [Cathode Ray Tube, isRegulatedFor, radiation safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegulatedFor Context triple: [Cathode Ray Tube, isRegulatedFor, radiation safety]
-
A.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
B.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
C.
hasRegulatedEntityType
Indicates that an entity is subject to regulation specifically because it belongs to a particular regulated category or type.
-
D.
subjectToRegulation
chosen
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
E.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:57 p.m.