Triple
T1697136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Campaign Finance Board |
E36683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campaign finance regulatory body |
C3926
|
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: campaign finance regulatory body Context triple: [New York City Campaign Finance Board, instanceOf, campaign finance regulatory body]
-
A.
campaign finance regulatory agency
chosen
A campaign finance regulatory agency is a governmental or independent body responsible for overseeing, enforcing, and administering laws that govern the funding, disclosure, and spending of money in political campaigns to ensure transparency and prevent corruption.
-
B.
political donor
A political donor is an individual or organization that contributes money or resources to political candidates, parties, or causes to support their campaigns and influence public policy.
-
C.
election commission
An election commission is an authoritative body responsible for planning, organizing, supervising, and ensuring the fairness and legality of electoral processes within a jurisdiction.
-
D.
lobbyist
A lobbyist is a professional advocate who seeks to influence public policy and decision-making on behalf of individuals, organizations, or interest groups by communicating with legislators and government officials.
-
E.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.