Triple
T23520946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDLP |
E574504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government information dissemination program |
C357
|
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: government information dissemination program Context triple: [FDLP, instanceOf, government information dissemination program]
-
A.
government program category
A government program category is a classification that groups public initiatives, services, or funding efforts based on their shared policy goals, target populations, or functional areas.
-
B.
e-government program
An e-government program is an organized initiative that uses digital technologies to deliver public services, enhance government operations, and improve interaction between government, citizens, and businesses.
-
C.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
D.
government statistical program
A government statistical program is an organized, ongoing initiative by a public agency to systematically collect, process, analyze, and disseminate data on specific aspects of the population, economy, or environment to inform policy and public understanding.
-
E.
program of a state government agency
A program of a state government agency is an organized set of activities, services, and resources designed and managed by the agency to achieve specific public policy goals or deliver particular benefits to residents within the state.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:08 p.m.