Triple
T10448252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrorist Screening Center |
E246348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-agency organization |
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 organization Context triple: [Terrorist Screening Center, instanceOf, multi-agency organization]
-
A.
multi-agency partnership
chosen
A multi-agency partnership is a collaborative arrangement in which multiple organizations from different sectors coordinate resources, expertise, and decision-making to achieve shared goals that no single agency could accomplish as effectively alone.
-
B.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
C.
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.
-
D.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
E.
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.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:16 p.m.