Triple
T7461137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series EE savings bond |
E176250
|
entity |
| Predicate | interestTaxation |
P3166
|
FINISHED |
| Object | subject to federal income tax |
—
|
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: subject to federal income tax | Statement: [Series EE savings bond, interestTaxation, subject to federal income tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interestTaxation Context triple: [Series EE savings bond, interestTaxation, subject to federal income tax]
-
A.
positionOnTaxes
Indicates a stance or viewpoint an entity holds regarding tax policies or taxation issues.
-
B.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
C.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
-
D.
taxCase
Indicates a legal case or proceeding whose primary subject is taxation or tax-related disputes between parties.
-
E.
positionOnTaxation
Indicates a stance or viewpoint an entity holds regarding tax policies, levels, or structures.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d6cf8c8190a31cac121d151d78 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.