Triple
T10340421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hays Office |
E243113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | self-regulatory body |
C1914
|
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: self-regulatory body Context triple: [Hays Office, instanceOf, self-regulatory body]
-
A.
self-regulatory organization
chosen
A self-regulatory organization is an entity, typically within a specific industry or profession, that creates and enforces rules and standards for its members to promote fair, ethical, and orderly conduct, often under the oversight of a governmental authority.
-
B.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
C.
standards-setting organization
A standards-setting organization is an entity that develops, maintains, and promotes agreed-upon technical, professional, or procedural norms to ensure compatibility, quality, and interoperability across industries or sectors.
-
D.
disciplinary inspection body
A disciplinary inspection body is an organizational unit responsible for monitoring, investigating, and enforcing compliance with rules, ethics, and standards within an institution or system.
-
E.
self-governing organization
A self-governing organization is an entity that independently establishes and enforces its own rules, structures, and decision-making processes without external control.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:54 a.m.