Triple
T9851787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Task Force on Consumer Compliance |
E239486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interagency task force |
C15271
|
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: interagency task force Context triple: [Task Force on Consumer Compliance, instanceOf, interagency task force]
-
A.
counterterrorism task force
A counterterrorism task force is a specialized, multi-agency group organized to prevent, detect, and respond to terrorist threats and activities through intelligence gathering, operational coordination, and targeted interventions.
-
B.
interstate agency
An interstate agency is an organization formed by two or more states through a formal agreement to collaboratively manage shared resources, services, or regulatory responsibilities across their borders.
-
C.
intergovernmental working group
chosen
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.
-
D.
intergovernmental coordination agency
An intergovernmental coordination agency is an organization formed by multiple governments to align policies, share information, and manage joint initiatives across jurisdictions.
-
E.
interstate council
An interstate council is a formal collaborative body composed of representatives from multiple states or jurisdictions that coordinates policies, resolves shared issues, and facilitates joint decision-making across state boundaries.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:34 p.m.