Triple
T6175445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Historic Preservation Tax Incentives program in California |
E137806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-administered federal program |
C4337
|
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: state-administered federal program Context triple: [Federal Historic Preservation Tax Incentives program in California, instanceOf, state-administered federal program]
-
A.
federal government program
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.
-
B.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
-
C.
United States federal government program
A United States federal government program is an organized set of activities, services, or regulations funded and administered by federal agencies to implement national policies and address public needs.
-
D.
state-run initiative
A state-run initiative is a government-organized and funded program or project designed to achieve specific public policy goals or deliver services to citizens.
-
E.
state incentive program
chosen
A state incentive program is a government-sponsored initiative that offers financial or regulatory benefits to individuals, businesses, or organizations to encourage specific behaviors or investments that align with public policy goals.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:18 p.m.