Triple
T13273525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US0846707026 |
E316127
|
entity |
| Predicate | dividendEligibility |
P109268
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [US0846707026, dividendEligibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividendEligibility Context triple: [US0846707026, dividendEligibility, yes]
-
A.
dividendEntitlement
Indicates that one entity has the right to receive dividend payments associated with another entity.
-
B.
dividendType
Indicates the classification of a dividend based on its nature or form (e.g., cash, stock, special), specifying what kind of dividend is being distributed.
-
C.
includesDividends
Indicates that the referenced value or calculation already accounts for dividend payments in its total.
-
D.
isDividendAristocrat
Indicates that an entity has consistently increased its dividend payouts for a long, defined period, qualifying it as a “dividend aristocrat.”
-
E.
dividendFrequency
Indicates how often dividend payments are scheduled or distributed over a given period.
- F. None of above. chosen
Provenance (4 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.