Triple
T1427783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P 500 ETFs |
E30371
|
entity |
| Predicate | incomeSource |
P13615
|
FINISHED |
| Object | stock dividends |
—
|
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: stock dividends | Statement: [S&P 500 ETFs, incomeSource, stock dividends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incomeSource Context triple: [S&P 500 ETFs, incomeSource, stock dividends]
-
A.
incomeType
Indicates the category or source classification of an entity’s income within a given context.
-
B.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
C.
incomeTreatment
Indicates a relationship where an entity receives, is subject to, or is affected by a particular income-related treatment, policy, or classification.
-
D.
revenueSources
chosen
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.