Triple
T108422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Markets Tax Credit Program |
E2188
|
entity |
| Predicate | taxpayerBenefitForm |
P7915
|
FINISHED |
| Object | nonrefundable tax credit |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: nonrefundable tax credit | Statement: [New Markets Tax Credit Program, taxpayerBenefitForm, nonrefundable tax credit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxpayerBenefitForm Context triple: [New Markets Tax Credit Program, taxpayerBenefitForm, nonrefundable tax credit]
-
A.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
C.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
D.
benefitedCountry
Indicates that one country gains an advantage, profit, or positive outcome from an action, event, or entity associated with another.
-
E.
usedInTaxPayments
Indicates that something is employed or applied as part of making or fulfilling tax payments.
- F. None of above. chosen
Provenance (4 batches)
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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25a1199ac8190ac65ffaaf45b4f5b |
completed | Feb. 28, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69a2563e7188819091e9a94e071991d7 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25a10d6448190bee47847d5c13b84 |
completed | Feb. 28, 2026, 2:59 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.