Triple
T22405045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Group of Enforcement Officers |
E553858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory working group |
C46235
|
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: regulatory working group Context triple: [Working Group of Enforcement Officers, instanceOf, regulatory working group]
-
A.
collaborative working group
A collaborative working group is a coordinated team of individuals who share responsibilities, knowledge, and decision-making to achieve a common goal or complete a specific project.
-
B.
intergovernmental working group
An intergovernmental working group is a collaborative body composed of representatives from multiple governments tasked with developing, coordinating, or advising on policies, standards, or actions in a specific issue area.
-
C.
rule‑making committee
A rule‑making committee is a group formally tasked with developing, reviewing, and approving rules or regulations that govern the behavior, procedures, or operations of an organization or system.
-
D.
intergovernmental working group framework
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
-
E.
regional representative group
A regional representative group is an organized body of individuals chosen or appointed to advocate for and make decisions on behalf of stakeholders within a specific geographic area.
- F. None of above. chosen
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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:46 p.m.