Triple
T22029661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form W-7 (renewal) |
E544051
|
entity |
| Predicate | taxDomain |
P3166
|
FINISHED |
| Object | individual 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: individual income tax | Statement: [Form W-7 (renewal), taxDomain, individual income tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxDomain Context triple: [Form W-7 (renewal), taxDomain, individual income tax]
-
A.
taxingJurisdiction
Indicates the authority or region that has the legal power to impose and collect taxes on a given entity or transaction.
-
B.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
-
C.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
D.
taxId
Indicates that an entity is associated with a specific taxonomic identifier used to uniquely reference its position in a taxonomic classification system.
-
E.
taxRegime
Indicates the system or structure of taxation that governs how taxes are assessed, collected, and applied within a particular context or jurisdiction.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ebf6d48190b84e7a45bbf9049c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.