Triple
T36977587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Other Dependent Credit |
E914741
|
entity |
| Predicate | effectiveForTaxYearsBeginning |
P132554
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Other Dependent Credit, effectiveForTaxYearsBeginning, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveForTaxYearsBeginning Context triple: [Other Dependent Credit, effectiveForTaxYearsBeginning, 2018]
-
A.
appliesToTaxYear
Indicates the specific tax year or fiscal period to which a tax-related rule, record, or obligation is applicable.
-
B.
effectiveForAnnualPeriodsBeginningOnOrAfter
chosen
Indicates that something (such as a rule, standard, or requirement) applies starting from annual reporting periods whose first day is on or after a specified date.
-
C.
introducedInTaxYear
Indicates that something (such as a rule, benefit, or provision) first became applicable or was brought into effect in a specified tax year.
-
D.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
E.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 3, 2026, 4:14 p.m.