Triple
T14828800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of New York government budget |
E348642
|
entity |
| Predicate | majorRevenueType |
P7220
|
FINISHED |
| Object | personal 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: personal income tax | Statement: [State of New York government budget, majorRevenueType, personal income tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRevenueType Context triple: [State of New York government budget, majorRevenueType, personal income tax]
-
A.
majorRevenueSource
chosen
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
B.
revenueSources
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
C.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
D.
majorTradeType
Indicates the primary category or kind of trade activity that characterizes the relationship between the involved entities.
-
E.
revenueLevel
Indicates the relative amount or tier of revenue associated with an entity or activity.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0737d4c8190a49bf6b013da208c |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.