Triple
T16657308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Client Security Fund |
E404763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal profession regulatory program |
C18581
|
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: legal profession regulatory program Context triple: [Client Security Fund, instanceOf, legal profession regulatory program]
-
A.
professional regulation law
chosen
Professional regulation law governs the standards, licensing, oversight, and disciplinary processes for individuals and entities in regulated professions to protect the public interest and ensure ethical, competent practice.
-
B.
legal discipline
A legal discipline is a specialized branch of law that focuses on a particular area of legal rules, principles, and practices, such as criminal law, contract law, or constitutional law.
-
C.
law qualification
Law qualification is a formal credential or status that certifies an individual has met the educational, professional, and regulatory requirements to practice law within a specific jurisdiction.
-
D.
professional legal training institution
A professional legal training institution is an organization dedicated to preparing individuals for legal practice through specialized education, skills development, and practical training aligned with professional standards and licensing requirements.
-
E.
health law program
A health law program is an academic or training course of study that focuses on the legal, regulatory, and ethical issues governing healthcare systems, providers, patients, and public health policy.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:18 a.m.