Triple
T7846196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1099-NEC |
E181927
|
entity |
| Predicate | reportsIncomeType |
P24934
|
FINISHED |
| Object | nonemployee compensation |
—
|
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: nonemployee compensation | Statement: [Form 1099-NEC, reportsIncomeType, nonemployee compensation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsIncomeType Context triple: [Form 1099-NEC, reportsIncomeType, nonemployee compensation]
-
A.
incomeType
chosen
Indicates the category or source classification of an entity’s income within a given context.
-
B.
incomeTreatment
Indicates a relationship where an entity receives, is subject to, or is affected by a particular income-related treatment, policy, or classification.
-
C.
income
Indicates the amount of money an entity receives, typically over a specified period, from work, investments, or other sources.
-
D.
reportType
Indicates the specific category or kind of report associated with an entity or action.
-
E.
incomeCounted
Indicates that a specified amount of income is included in a particular calculation, assessment, or determination (such as eligibility, benefits, or totals).
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163f5da08190b7340ef4cc01cd19 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.