Triple
T27899622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schedule SE (Form 1040) |
E705591
|
entity |
| Predicate | governsTaxType |
P3166
|
FINISHED |
| Object | self-employment Social Security 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: self-employment Social Security tax | Statement: [Schedule SE (Form 1040), governsTaxType, self-employment Social Security tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTaxType Context triple: [Schedule SE (Form 1040), governsTaxType, self-employment Social Security tax]
-
A.
taxType
chosen
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
-
C.
typeOfTaxCredit
Indicates that one entity is a specific kind or category of tax credit in relation to another entity.
-
D.
introducedTaxType
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
-
E.
taxingJurisdiction
Indicates the authority or region that has the legal power to impose and collect taxes on a given entity or transaction.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 27, 2026, 6:41 p.m.