Triple
T2020490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FATCA Form 8938 |
E44092
|
entity |
| Predicate | effectiveTaxYear |
P23631
|
FINISHED |
| Object | tax years beginning after March 18 2010 |
—
|
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: tax years beginning after March 18 2010 | Statement: [FATCA Form 8938, effectiveTaxYear, tax years beginning after March 18 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveTaxYear Context triple: [FATCA Form 8938, effectiveTaxYear, tax years beginning after March 18 2010]
-
A.
effectiveYear
chosen
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
B.
declaredYear
Indicates the year in which something was formally announced, established, or proclaimed.
-
C.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
fiscalYearEnd
Indicates the date or point in time when an entity’s fiscal or financial reporting year concludes.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.