Triple
T13236655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 97-34 |
E315162
|
entity |
| Predicate | increasedEstateTaxExemption |
P52500
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Public Law 97-34, increasedEstateTaxExemption, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: increasedEstateTaxExemption Context triple: [Public Law 97-34, increasedEstateTaxExemption, true]
-
A.
changesEstateTaxExemption
chosen
Indicates that an action or policy alters the threshold amount of an estate that is exempt from estate taxation.
-
B.
eliminatesPersonalExemptions
Indicates that a policy or action removes previously available personal tax exemptions for individuals.
-
C.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
-
D.
stateAndLocalTaxDeductionCap
Indicates a limit on the amount of state and local taxes that can be deducted, typically for income tax purposes.
-
E.
changesIndividualIncomeTaxBrackets
Indicates that an action or policy alters the structure or thresholds of individual income tax brackets.
- F. None of above.
Provenance (3 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d56da008190af55da3a9e7ffd4d |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.