Triple
T2664412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Card Scheme |
E55600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | adverse event reporting system |
C3767
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: adverse event reporting system Context triple: [Yellow Card Scheme, instanceOf, adverse event reporting system]
-
A.
public warning system
A public warning system is an organized infrastructure of technologies, protocols, and communication channels designed to rapidly alert and inform the public about imminent or ongoing emergencies and hazards.
-
B.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
C.
auditing system
An auditing system is a software component that systematically collects, records, and analyzes events or transactions within a system to ensure accountability, traceability, and compliance with policies or regulations.
-
D.
regulatory reporting platform
chosen
A regulatory reporting platform is a system that collects, validates, and transforms organizational data into compliant reports for submission to regulators according to applicable rules and deadlines.
-
E.
environmental health risk assessment program
An environmental health risk assessment program systematically evaluates potential adverse health effects from environmental hazards by analyzing exposure, toxicity, and population vulnerability to inform risk management decisions.
- F. None of above.
Provenance (1 batch)
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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.