Triple
T24730010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspection générale des finances |
E618257
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | service d’audit public |
C3533
|
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: service d’audit public Context triple: [Inspection générale des finances, instanceOf, service d’audit public]
-
A.
Public service
Public service is the provision of essential goods, support, and regulatory functions by government or community organizations to promote the well-being, safety, and equitable treatment of the public.
-
B.
auditing institution
chosen
An auditing institution is an independent organization responsible for systematically examining and evaluating financial records, operations, and controls to ensure accuracy, compliance, and accountability.
-
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.
federal public service of Belgium
The federal public service of Belgium is the central administrative apparatus of the Belgian federal state, responsible for preparing, implementing, and managing federal policies, legislation, and public services across various domains such as finance, justice, interior affairs, and social security.
-
E.
revenue service
A revenue service is a governmental or organizational entity responsible for assessing, collecting, and enforcing taxes or other forms of income to fund public operations and services.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
Created at: April 18, 2026, 4:02 a.m.