Triple
T5399764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Terrorism Task Force |
E120743
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-agency partnership |
C18021
|
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: multi-agency partnership Context triple: [Joint Terrorism Task Force, instanceOf, multi-agency partnership]
-
A.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
B.
bi-county agency
A bi-county agency is a governmental or quasi-governmental organization established to provide shared services, regulation, or administration across two adjacent counties.
-
C.
inter-district collaborative
An inter-district collaborative is a structured partnership among multiple school districts that share resources, expertise, and decision-making to improve educational services and outcomes across their combined communities.
-
D.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
E.
public social services agency
A public social services agency is a government-funded organization that provides assistance, protection, and support programs to individuals and families in need to promote their well-being and social stability.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:04 p.m.