Triple
T16115828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 115-97 |
E390998
|
entity |
| Predicate | temporarilyIncreases |
P96423
|
FINISHED |
| Object | estate tax exemption |
—
|
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: estate tax exemption | Statement: [Public Law 115-97, temporarilyIncreases, estate tax exemption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyIncreases Context triple: [Public Law 115-97, temporarilyIncreases, estate tax exemption]
-
A.
wasTemporarilyIncreasedBy
chosen
Indicates that the value or level of something was raised for a limited period of time by a specified agent or cause.
-
B.
subsequentIncrease
Indicates that one quantity or value increases after a prior event, state, or change has occurred.
-
C.
increases
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
D.
firstIncreaseIn
Indicates the point or event at which a quantity or value begins to increase for the first time in a given sequence or process.
-
E.
increasesWith
Indicates that as the value or magnitude of one entity grows, the value or magnitude of another entity correspondingly grows as well.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016a9dd48190bca3f58778ed865f |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.