Triple
T31123244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schedule B (Form 1040) |
E793277
|
entity |
| Predicate | requiresTaxpayerInformation |
P12650
|
FINISHED |
| Object | name |
—
|
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: name | Statement: [Schedule B (Form 1040), requiresTaxpayerInformation, name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTaxpayerInformation Context triple: [Schedule B (Form 1040), requiresTaxpayerInformation, name]
-
A.
requiresTaxpayerIdentification
Indicates that providing a taxpayer identification number or equivalent tax-related identifier is necessary for the related entity, transaction, or process.
-
B.
requiresPayerInformation
Indicates that the action or process cannot proceed unless specific information about the payer has been provided.
-
C.
requiredInformation
chosen
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
D.
typeOfTaxpayerCovered
Indicates the category or kind of taxpayer to which a particular rule, obligation, or provision applies.
-
E.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: April 29, 2026, 9:05 p.m.